Once you got the Authorization Code from Step 1 click the Exchange authorization code
up vote
0
down vote
favorite
I am not sure why i am getting this error message. i have inserted the ids
POST /oauth2/v4/token HTTP/1.1
Host: www.googleapis.com
Content-length: 322
content-type: application/x-www-form-urlencoded
user-agent: google-oauth-playground
HTTP/1.1 400 Bad Request
Content-length: 68
X-xss-protection: 1; mode=block
X-content-type-options: nosniff
Transfer-encoding: chunked
Vary: Origin, X-Origin, Referer
Server: ESF
-content-encoding: gzip
Cache-control: private
Date: Sun, 11 Nov 2018 23:59:34 GMT
X-frame-options: SAMEORIGIN
Alt-svc: quic=":443"; ma=2592000; v="44,43,39,35"
Content-type: application/json; charset=utf-8
{
"error_description": "Bad Request",
"error": "invalid_grant"
}
google-oauth asked Nov 12 at 0:15
Samson
1
add a comment |
up vote
0
down vote
favorite
I am not sure why i am getting this error message. i have inserted the ids
POST /oauth2/v4/token HTTP/1.1
Host: www.googleapis.com
Content-length: 322
content-type: application/x-www-form-urlencoded
user-agent: google-oauth-playground
HTTP/1.1 400 Bad Request
Content-length: 68
X-xss-protection: 1; mode=block
X-content-type-options: nosniff
Transfer-encoding: chunked
Vary: Origin, X-Origin, Referer
Server: ESF
-content-encoding: gzip
Cache-control: private
Date: Sun, 11 Nov 2018 23:59:34 GMT
X-frame-options: SAMEORIGIN
Alt-svc: quic=":443"; ma=2592000; v="44,43,39,35"
Content-type: application/json; charset=utf-8
{
"error_description": "Bad Request",
"error": "invalid_grant"
}
asked Nov 12 at 0:15
Samson
1
please edit your question to explain the steps you have taken to get to the moment you see this error.
– pinoyyid
Nov 12 at 20:39
Include the data in the HTTP body section. As the error states yourgrantrequest is not valid.grant_typewill look likegrant_type: urn:ietf:params:oauth:grant-type:jwt-bearerorgrant_type: refresh_tokenbefore encoding. The first is for requesting an access token the second for renewing an existing access token with a refresh token.
– John Hanley
Nov 14 at 1:23
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am not sure why i am getting this error message. i have inserted the ids
POST /oauth2/v4/token HTTP/1.1
Host: www.googleapis.com
Content-length: 322
content-type: application/x-www-form-urlencoded
user-agent: google-oauth-playground
HTTP/1.1 400 Bad Request
Content-length: 68
X-xss-protection: 1; mode=block
X-content-type-options: nosniff
Transfer-encoding: chunked
Vary: Origin, X-Origin, Referer
Server: ESF
-content-encoding: gzip
Cache-control: private
Date: Sun, 11 Nov 2018 23:59:34 GMT
X-frame-options: SAMEORIGIN
Alt-svc: quic=":443"; ma=2592000; v="44,43,39,35"
Content-type: application/json; charset=utf-8
{
"error_description": "Bad Request",
"error": "invalid_grant"
}
asked Nov 12 at 0:15
Samson
1
I am not sure why i am getting this error message. i have inserted the ids
POST /oauth2/v4/token HTTP/1.1
Host: www.googleapis.com
Content-length: 322
content-type: application/x-www-form-urlencoded
user-agent: google-oauth-playground
HTTP/1.1 400 Bad Request
Content-length: 68
X-xss-protection: 1; mode=block
X-content-type-options: nosniff
Transfer-encoding: chunked
Vary: Origin, X-Origin, Referer
Server: ESF
-content-encoding: gzip
Cache-control: private
Date: Sun, 11 Nov 2018 23:59:34 GMT
X-frame-options: SAMEORIGIN
Alt-svc: quic=":443"; ma=2592000; v="44,43,39,35"
Content-type: application/json; charset=utf-8
{
"error_description": "Bad Request",
"error": "invalid_grant"
}
asked Nov 12 at 0:15
Samson
1
asked Nov 12 at 0:15
Samson
1
asked Nov 12 at 0:15
Samson
1
asked Nov 12 at 0:15
Samson
1
asked Nov 12 at 0:15
Samson
1
1
please edit your question to explain the steps you have taken to get to the moment you see this error.
– pinoyyid
Nov 12 at 20:39
Include the data in the HTTP body section. As the error states yourgrantrequest is not valid.grant_typewill look likegrant_type: urn:ietf:params:oauth:grant-type:jwt-bearerorgrant_type: refresh_tokenbefore encoding. The first is for requesting an access token the second for renewing an existing access token with a refresh token.
– John Hanley
Nov 14 at 1:23
add a comment |
please edit your question to explain the steps you have taken to get to the moment you see this error.
– pinoyyid
Nov 12 at 20:39
Include the data in the HTTP body section. As the error states yourgrantrequest is not valid.grant_typewill look likegrant_type: urn:ietf:params:oauth:grant-type:jwt-bearerorgrant_type: refresh_tokenbefore encoding. The first is for requesting an access token the second for renewing an existing access token with a refresh token.
– John Hanley
Nov 14 at 1:23
please edit your question to explain the steps you have taken to get to the moment you see this error.
– pinoyyid
Nov 12 at 20:39
please edit your question to explain the steps you have taken to get to the moment you see this error.
– pinoyyid
Nov 12 at 20:39
Include the data in the HTTP body section. As the error states your
grant request is not valid. grant_type will look like grant_type: urn:ietf:params:oauth:grant-type:jwt-bearer or grant_type: refresh_token before encoding. The first is for requesting an access token the second for renewing an existing access token with a refresh token.– John Hanley
Nov 14 at 1:23
Include the data in the HTTP body section. As the error states your
grant request is not valid. grant_type will look like grant_type: urn:ietf:params:oauth:grant-type:jwt-bearer or grant_type: refresh_token before encoding. The first is for requesting an access token the second for renewing an existing access token with a refresh token.– John Hanley
Nov 14 at 1:23
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Bad Request error occurs when the request syntax are wrong (i.e. when a parameter or a header you are supposed to send is missing or contains an incorrect/invalid value). Best option is to check OAuth Specification are figure out what you have done wrong in the token request. Google might have a slightly different implementation from the actual specification, but I think it won't be difficult to find the issue after checking the documentation.
Access token request specification for authorization code grant can be found here.
answered Nov 12 at 4:19
RakihthaRR
18911
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Bad Request error occurs when the request syntax are wrong (i.e. when a parameter or a header you are supposed to send is missing or contains an incorrect/invalid value). Best option is to check OAuth Specification are figure out what you have done wrong in the token request. Google might have a slightly different implementation from the actual specification, but I think it won't be difficult to find the issue after checking the documentation.
Access token request specification for authorization code grant can be found here.
answered Nov 12 at 4:19
RakihthaRR
18911
add a comment |
up vote
0
down vote
Bad Request error occurs when the request syntax are wrong (i.e. when a parameter or a header you are supposed to send is missing or contains an incorrect/invalid value). Best option is to check OAuth Specification are figure out what you have done wrong in the token request. Google might have a slightly different implementation from the actual specification, but I think it won't be difficult to find the issue after checking the documentation.
Access token request specification for authorization code grant can be found here.
answered Nov 12 at 4:19
RakihthaRR
18911
add a comment |
up vote
0
down vote
up vote
0
down vote
Bad Request error occurs when the request syntax are wrong (i.e. when a parameter or a header you are supposed to send is missing or contains an incorrect/invalid value). Best option is to check OAuth Specification are figure out what you have done wrong in the token request. Google might have a slightly different implementation from the actual specification, but I think it won't be difficult to find the issue after checking the documentation.
Access token request specification for authorization code grant can be found here.
answered Nov 12 at 4:19
RakihthaRR
18911
Bad Request error occurs when the request syntax are wrong (i.e. when a parameter or a header you are supposed to send is missing or contains an incorrect/invalid value). Best option is to check OAuth Specification are figure out what you have done wrong in the token request. Google might have a slightly different implementation from the actual specification, but I think it won't be difficult to find the issue after checking the documentation.
Access token request specification for authorization code grant can be found here.
answered Nov 12 at 4:19
RakihthaRR
18911
answered Nov 12 at 4:19
RakihthaRR
18911
answered Nov 12 at 4:19
RakihthaRR
18911
answered Nov 12 at 4:19
RakihthaRR
18911
18911
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254543%2fonce-you-got-the-authorization-code-from-step-1-click-the-exchange-authorization%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
please edit your question to explain the steps you have taken to get to the moment you see this error.
– pinoyyid
Nov 12 at 20:39
Include the data in the HTTP body section. As the error states your
grantrequest is not valid.grant_typewill look likegrant_type: urn:ietf:params:oauth:grant-type:jwt-bearerorgrant_type: refresh_tokenbefore encoding. The first is for requesting an access token the second for renewing an existing access token with a refresh token.– John Hanley
Nov 14 at 1:23