Solved: Verification of apps already in production use

yutaka-takai · 01-18-2023 11:23 PM

The app is already running in a production environment and there are users using it.
However, we have found that the status on the console's OAuth consent screen is 'Needs verification', so we are preparing to verify the app.
In this context, there are a few things I would like to check before verifying the app, so I am submitting this.

The following are the things we want to check.

During the app verification, will the content displayed on the OAuth authentication screen change?
After the app is validated, what happens if the scope applied for is not enough than the scope already in use?
Can the token information already authenticated be used as it is?

The text was translated using translation software, so we apologise if there are any mistakes.

dionv

Hello yutaka-takai,

Regarding about your questions:

During the app verification, will the content displayed on the OAuth authentication screen change? When you use OAuth 2.0 for authorization, Google displays a consent screen to the user including a summary of your project, its policies, and the requested authorization scopes of access. Configuring your app's OAuth consent screen defines what is displayed to users and app reviewers, and registers your app so you can publish it later.
After the app is validated, what happens if the scope applied for is not enough than the scope already in use? When an application exceeds the rate limit, Error 403: rate_limit_exceeded is displayed to users.
Can the token information already authenticated be used as it is? If you use Application Default Credentials (ADC) and the Cloud Client Libraries or Google API Client Libraries, you do not need to manage access tokens; the libraries automatically retrieve the credential, exchange it for an access token, and refresh the access token as needed. You can refer to this documentation for more details.

View solution in original post

dionv

Hello yutaka-takai,

Regarding about your questions:

During the app verification, will the content displayed on the OAuth authentication screen change? When you use OAuth 2.0 for authorization, Google displays a consent screen to the user including a summary of your project, its policies, and the requested authorization scopes of access. Configuring your app's OAuth consent screen defines what is displayed to users and app reviewers, and registers your app so you can publish it later.
After the app is validated, what happens if the scope applied for is not enough than the scope already in use? When an application exceeds the rate limit, Error 403: rate_limit_exceeded is displayed to users.
Can the token information already authenticated be used as it is? If you use Application Default Credentials (ADC) and the Cloud Client Libraries or Google API Client Libraries, you do not need to manage access tokens; the libraries automatically retrieve the credential, exchange it for an access token, and refresh the access token as needed. You can refer to this documentation for more details.

yutaka-takai

Hello, dionv

thank you for your reply.

I will check the link destination and apply for the application.