Bobcares

Google Cloud OAuth Consent Screen: Explained

by | Jul 24, 2022

Google cloud OAuth consent screen specifies what the app is shown to users and app reviewers and registers it for publishing later.

Bobcares answers all questions no matter the size, as part of our Google cloud platform support Service

Let us take a look at Google Cloud OAuth Consent Screen in detail.

OAuth consent screengoogle cloud oauth consent screen

Google shows the user a consent page that includes an overview of the project, its policies, and the desired authorized scopes of access when utilizing OAuth 2.0 for authorization. The OAuth consent screen configuration for the app specifies what is shown to users and app reviewers and registers the app for subsequent publication.

All OAuth 2.0 applications require a consent screen setup, however, only apps used by users outside of the Google Workspace organization must list scopes. When a service account is created, the Google project must have an OAuth Consent Screen constructed and configured to allow Google Workspace Domain-Wide Delegation.

Configure OAuth consent & app registration

To configure the OAth consent and register the app on google cloud follow the steps given below:

  1. Firstly, Open the Google Cloud console.
  2. Click Menu > APIs & Services > Google OAuth consent screen in the top-left corner.
  3. Then, choose a user type for the app and then click Create.
  4. After completing the app registration form, click Save and Continue.
  5. Click Add or Remove Scopes if the user is developing an app for usage outside of the Google Workspace organization. Add and confirm the app’s authorization scopes, then click Save and Continue. Please keep in mind that some scopes require further Google reviews. Scopes will not display on the consent page for exclusively internal applications by the Google Workspace organization. And the use of restricted or sensitive scopes does not require additional assessment by Google.
  6. Click Add users under “Test users.” Enter the email address and the names of any more approved test users, then click Save and Continue.
  7. Examine the app registration summary. To make changes, click Edit, or return to the Dashboard. This is the final step in configuring the google cloud OAuth consent screen.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude, it is easy to configure and register the apps through the Google cloud OAuth consent seen. The feature is accessible through the Google cloud console.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF