CODEWITHSUNDEEP
google-oauth
TJC
TJC

Reputation: 727

Occasionally Missing Return Parameter id_token

When using the Google OAuth2 API, I am receiving inconsistent reply parameters.

scopes: ['email','profile']

Expected Response:

{ 
  access_token: 'ya29.fQB...aYSwXTK7Etm2XzIhA2VYf7Gtp',
  token_type: 'Bearer',
  expires_in: 3600,
  id_token: 'eyJhbGciOiJSUzI1NiIsI...bDkzZDNjYzFicWJmdTIzdjF...pZWRfZW1h...0vYWNjb3Vud...kSObTnsLQKg...3Mpg6Y2K2Bhw6c' 
}

Received Response:

{ 
  access_token: 'ya29.fQDvVUn66q...vqe2WLQf_Nc4d4oc',
  token_type: 'Bearer',
  expires_in: 3600 
}

Does anybody know how to solve this problem or work around it?

Upvotes: 3

Views: 559

Answers (3)

Nabeel Hendow
Nabeel Hendow

Reputation: 9

For us to be prepared, Are you/Google planning on removing the email ID from the Google API in the future, or was that a development bug that was corrected? Thanx,

Upvotes: 0

Nabeel Hendow
Nabeel Hendow

Reputation: 9

Thanx for the clarification Naveen, Amplify.com education application faced this issue around 2:30pm Sep 11, 2014 Eastern and it was fixed around 5:15pm EST same day. Our authentication is based on Google OAuth.

Upvotes: 0

nvnagr
nvnagr

Reputation: 2063

Sorry, this was caused by an issue with our latest release and we rolled back as soon as we came to know about it. So this should be resolved (as of 2pm PST). If you are still seeing issues do let us know.

Upvotes: 1

Related Questions