Sometimes missing return parameter id_token

I am getting inconsistent response parameters when using the Google OAuth2 API.

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 answer:

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

      

Does anyone know how to fix this problem or work around it?

+3


source to share


3 answers


Sorry this was caused by a problem with our latest version and we rolled back as soon as we found out about it. Therefore, it should be allowed (starting at 2pm PST). If you still see problems, please let us know.



+1


source


Thanx for Naveen's clarification, Amplify.com's education app ran into this issue around 2:30 pm ET on September 11, 2014, and it was recorded at 5:15 pm ET on the same day. Our authentication is based on Google OAuth.



0


source


To get us ready, are you planning on / Google to remove the email id from the Google API in the future, or have there been any development bug fixes? Thanx,

0


source







All Articles