You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wonderfly opened this issue
Jan 9, 2015
· 1 comment
Assignees
Labels
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
Using a bad scope in assertion profile code will result in an invalid_scope error (and 4xx response) from the OAuth token endpoint. The Java client library currently seems to ignore this error, and instead proceeds to make the call to the actual API service with an empty OAuth access token.
If there is an error in obtaining an access token using the assertion profile, I'd expect this to be thrown to the top level to enable easier debugging of issues using service accounts.
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
From rmis...@google.com on June 06, 2012 09:57:46
Reported by ryanboyd:
Using a bad scope in assertion profile code will result in an invalid_scope error (and 4xx response) from the OAuth token endpoint. The Java client library currently seems to ignore this error, and instead proceeds to make the call to the actual API service with an empty OAuth access token.
If there is an error in obtaining an access token using the assertion profile, I'd expect this to be thrown to the top level to enable easier debugging of issues using service accounts.
Original issue: http://code.google.com/p/google-oauth-java-client/issues/detail?id=42
The text was updated successfully, but these errors were encountered: