Google Identity Platform: Cannot exchange authorization code for refresh and access tokens

Question

I'm trying to get access to Google Drive API and I read documentation. My iOS app sends first request to ask for permission to endpoint https://accounts.google.com/o/oauth2/v2/auth.

User grants permission. I get a code. Next step is to authorization code for refresh and access tokens.

As for installed apps, I don't need to send client secret. In order to do that iOS app sends POST request to the endpoint:

https://www.googleapis.com/oauth2/v4/token

with headers:

Content-Type : application/x-www-form-urlencoded

body:

code={CODE_FROM_OAUTH_SERVER}&client_id={CLIENT_ID_FROM_CONSOLE}&redirect_uri={APP_BUNDLE_IDENTIFIER}:/code&grant_type=authorization_code

I get the response:

{
  "error": "unsupported_grant_type",
  "error_description": "Invalid grant_type: "
}

App is registered in Google console.

My question is am I doing something wrong?

Which type of credentials did you create on developer console? — Linda Lawton - DaImTo, May 30 '17 at 06:50
@DaImTo, credentials for installed apps, in my case - Create client ID -> iOS — Yurii Boiko, May 30 '17 at 07:57
@DaImTo, the whole point of this question - I don't want use libraries, if I would like to, I can simply use Firebase/Auth and it will do what I want, I want full understanding of what is happening — Yurii Boiko, May 30 '17 at 14:26

Alfran · Answer 1 · 2017-06-01T11:30:44.433

3

It is sending the specified data in a POST request to the HTTP server, same as when browser do when we fill a HTML form and do submit . This will cause to pass the data to the server using the content-type application/x-www-form-urlencoded.

You should try by changing the way you pass the OAuth parameters like client_id, ,redirect_uri, grant_type, etc.

Or should try making Native client of default type.

edited Jun 01 '17 at 11:30

answered Jun 01 '17 at 02:15

Alfran

1,301
1
10
19

1

I tried different ways and it didn't work, maybe you have concrete suggestions? Thanks in advance. – Yurii Boiko Jun 01 '17 at 08:36

score 0 · Answer 2 · edited Jun 01 '17 at 15:16

0

One possible source of parsing errors is the redirect_uri . It should be url-encoded.

edited Jun 01 '17 at 15:16

Alfran

1,301
1
10
19

answered Jun 01 '17 at 04:34

Rondo

3,458
28
26

1

Yes, I have added URL encoding, it didn't help – Yurii Boiko Jun 01 '17 at 07:45

Google Identity Platform: Cannot exchange authorization code for refresh and access tokens

2 Answers2