![]() ![]() ![]() Projects configured with a publishing status of In production should complete the verification process, including defining scopes actively requested by your project's OAuth clients, if it meets one or more of the OAuth verification criteria, as described in Verification status. Your project's configuration may be subject to verification before its name and logo are displayed on an authorization screen or before it may request authorization of sensitive or restricted scopes. A project's publishing status is considered In production after selecting the Publish app button. Projects configured with a publishing status of In production are available to any user with a Google Account. A Google Workspace may control which third-party apps access its data or an account enrolled in Advanced Protection may block most non-Google apps. If your app requests any other OAuth scopes, then this exception does not apply.Ī test user may be unable to authorize scopes requested by your project's OAuth clients due to the availability of Google Services for the account or configured restrictions. If your app uses Sign in with Google to authenticate users then this exception also applies. For such requests, your users do not need to be in the trusted user list, they will not see a warning message, and their authorizations will not expire after 7 days. The only exception to this behavior is if your app requests a subset of the following: name, email address, and user profile (through the userinfo.email, userinfo.profile, openid scopes or their OpenID Connect equivalents). If your OAuth client requests an offline access type and receives a refresh token, that token will also expire.Ī Brand Account may authorize scopes requested by your project's OAuth clients if a specified test user manages the Brand Account. The warning message confirms the user has test access to your project but should consider the risks associated with granting access to their data to an unverified app.Īuthorizations by a test user will expire seven days from the time of consent. Google will display a warning message before allowing a specified test user to authorize scopes requested by your project's OAuth clients. A test user consumes a project's test user quota once added to the project. Projects configured with a publishing status of Testing are limited to up to 100 test users listed in the OAuth consent screen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |