Skip to content
Contact us
  • There are no suggestions because the search field is empty.

How to update your Global Google Sign-In configuration

Update your Google Sign-In settings when changing your app domain to prevent login errors.

If you are using Google Sign-In and change your app’s domain, you must update your OAuth configuration in Google Cloud and confirm the new credentials in your Control Panel. If this is not updated correctly, users may see redirect URI mismatch or domain verification errors when logging in.

Requirements

  • Access to the Google Cloud project that owns your OAuth client ID

  • Domain verified in Google Search Console

  • Permissions to edit authentication settings in your Control Panel

How to update your Global Google Sign-In configuration

  1. Log in to Google Cloud Console, then go to APIs & Services > Credentials.

  2. Under OAuth 2.0 Client IDs, select the Web application client used by your app.

  3. Click the Branding tab (Google Auth Platform).

  4. Under Authorized Domains, add your new base domain (for example: auth.yourdomain.com).

    • Do not include https:// or any paths.

    • Click Save.

  5. In the same OAuth client settings, scroll to Authorized redirect URIs.

  6. Add your exact callback URL (for example: https://auth.yourdomain.com/app/oauth2/callback).

    • The URI must match exactly, including https and the full path.

  7. Click Save.

  8. Copy your Client ID and Client Secret from this OAuth client.

  9. Log in to your Control Panel.

  10. Go to Settings (left menu) > Account > Global Google Sign-In Configuration.

  11. Turn on Use your own domain.

  12. Paste the updated Client ID and Client Secret.

  13. Click Save.

  14. Updating these settings may sign out existing users. They will need to log in again.

Troubleshooting tips

  1. redirect_uri_mismatch error: The redirect URI in Google Cloud must match your callback URL exactly, including https and the full path.

  2. Old domain still appears on consent screen: Confirm the new domain is added under Authorized Domains and that your Google app is verified.

  3. Client ID not working: Make sure you are editing the correct Web application OAuth client.

  4. Users stuck in login loop: Double-check both Authorized Domains and Authorized redirect URIs for exact matches.