Learn more.Īpplication Homepage link: Shown on Sign In With Google consent screen and One-Tap GDPR compliant disclaimer information under the “Continue as” button. Your applications' links must be hosted on Authorized Domains. Learn more.Īuthorized domains: To protect you and your users, Google only allows applications that authenticate using OAuth to use Authorized Domains. It is generally a best practice to request scopes incrementally, at the time access is required, rather than up front. For the authentication, default scope (email, profile, openid) is sufficient, you don't need to add any sensitive scopes.

Scopes for Google APIs: Scopes allow your application to access your user's private Google data. This email address will be shown to users on the Sign In With Google consent screen when the user clicks the application name. Support email: Shown on the consent screen for user support and to G Suite administrators evaluating access to your application for their users. The logo is shown on Sign In With Google consent screen and on account settings, whereas it’s not shown on One Tap dialog. The application name will be shown on the One-tap dialog window.Īpplication logo: An image on the consent screen that will help users recognize your app. The name should accurately reflect your application and be consistent with the application name users see elsewhere. On the 'OAuth consent screen' page, fill out the form and click the “Save” button.Īpplication name: The name of the application asking for consent. If prompted, select the project you just created.Open the OAuth consent screen page of the Google APIs console.A client ID looks like the following example:ġīoth Sign In With Google and One Tap authentication include a consent screen which tells users the application requesting access to their data, what kind of data they are asked for and the terms that apply. Note: You need the client ID string that's displayed in theĬonsole to configure Sign In With Google and to verify ID tokens on yourīackend. Key Point: Add both and to the Authorized JavaScript origins box for local tests or Key Point: Google One Tap can only be displayed in HTTPS domains. to the Authorized JavaScript origins box. Local tests or development, you must add both and That Google One Tap can only be displayed in HTTPS domains. Your site's domain in the Authorized JavaScript origins box. If your project doesn't have a Web application-type client ID, clickĬreate credentials > OAuth client ID to create one. Sign In With Google button or Google One Tap, use the existing project and the web To do so, complete the following steps:Ĭreate or select a Google APIs project. To enable Sign In With Google on your website, you first need to set up your GoogleĪPI client ID. Setup your OAuth configuration and optionally configure your site Content Before you add Sign In With Google, One Tap, or Automatic sign-in to your website

Tap forms tutorial