auth/calendar scope doesn't show in OAuth Consent scopes list (yet users are asked to grant access to Calendar)

Question

It's completely possible I've misunderstood the situation with scopes and Google's OAuth Consent...but I'm seeing something quite unusual. I'm using Google Calendar API v3 with OAuth2 to gain access to users' Calendar data. However, when I look into the OAuth Consent settings in the Google Developer console for the project I don't see any calendar-related scopes, yet the user is asked for the correct scopes to be granted.

What I'd Expect To See

What I Actually See

My expectation is that without the auth/calendar (or other calendar-related scopes) there's no way for the customer to be shown the scopes during they OAuth Consent screen?

On thin ice here because I was actually unaware that the OAuth Consent Screen (console.cloud.google.com/apis/credentials/consent) includes a set of project-wide Scopes. When I've used Google services w/ Scopes, I've only ever defined the Scopes in code and not at the project-level. Are you defining the richer set of Scopes in your application? — DazWilkin
Please edit your question and include your code. The scopes requested fro m the user are in your code all dev console does is validate which ones you are allowed to use in your code — DaImTo

Ernesto U Ernesto U · Accepted Answer · 2019-10-18T19:19:27

The scopes granted to the application are for the service account, now when the users are using your application they need to allow it to access their Google accounts unless you are using domain wide delegation

auth/calendar scope doesn't show in OAuth Consent scopes list (yet users are asked to grant access to Calendar)

1 Answers