Recent change in api "https://www.googleapis.com/oauth2/v1/userinfo" output

[Roshan Dawrani]

Hi,

    Can someone please let me know where I can find the current status of the Google OAuth request made to "https://www.googleapis.com/oauth2/v1/userinfo?alt=json"?

    

Till a few weeks back, it used to return output of the form {"id": "123456789", "name": "Roshan Dawrani", "email":"roshan...@gmail.com","verified_email":true}, but now it returns only {"email":"roshan...@gmail.com","verified_email":true}. The "id" and the "name" attributes have gone away.

Can anyone throw some light on it please?

Cheers.

--
Roshan
Blog: http://roshandawrani.wordpress.com/
Twitter: @roshandawrani
Skype: roshandawrani

[Roshan Dawrani]

I should have added that scopes requested are: "https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email"

Have "id", "name" gone away from the response of "https://www.googleapis.com/oauth2/v1/userinfo?alt=json" on purpose?

Cheers.

[Marius Scurtescu]

Hi Roshan,

I just tested this and the output is as expected. Most likely you are not asking for the profile scope.

The alt=json parameter is not needed, json is the default.

Marius

[Roshan Dawrani]

Hi Marius,

I am asking for these scopes - "https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email"

Is there anything I have missed in scopes?

Cheers.

[Marius Scurtescu]

The scopes look OK. Are you properly encoding the space between them in the URL?

How does the URL look like? The request URL has no secrets in it, it is safe to email it.

Marius

[Roshan Dawrani]

Hi Marius,

Yes, it looks like a "scope" issue on our side. The "scope" configuration I showed earlier is not being applied correctly when we finally invoke Google's authorization URL. I will try to resolve that issue at our end first.

Thanks for taking a look into it.

Cheers.