​
Overview

Integrate Google’s social connection with your app using Corbado by configuring the Client ID and Client Secret in your Corbado project’s settings.

For a streamlined development experience, Corbado provides preconfigured shared OAuth credentials and redirect URIs for development instances, which require no further setup.

However, for production environments, it is necessary to establish your own Google developer account and generate unique OAuth credentials.

​
Preliminary Steps

​
Configuration Steps for Google Social Connection

  1. In the Corbado developer panel, navigate to Settings > User Interface > Social. Activate the Google option and ensure “Use custom credentials” is selected. Copy the Authorized Redirect URI for later use.

  1. Open the Google Cloud Platform console in a new window. Select your project and enable OAuth 2.0 support as per the official setup instructions. In the “Authorized redirect URIs” section, paste the URI copied from the Corbado developer panel.

  1. Create an OAuth client ID in the Google Cloud console. Once created, copy the Client ID and Client Secret.

  1. Return to the Corbado developer panel, and in the modal window, paste the Client ID and Client Secret you just obtained.

​
Recap

By following this guide, you should have:

  • Created an OAuth client ID in Google Cloud Platform.
  • Entered the authorized redirect URI as provided by the Corbado developer panel into the OAuth client ID.
  • Configured the proper Client ID and Client Secret in the Corbado developer panel based on the values obtained from Google Cloud Platform.

After configuring, click “Save” to apply your settings. Congratulations, the Google Social Connection is now active for your instance.

​
Transitioning to Production

Be aware that Google OAuth apps start in “Testing” status, which is suitable for internal testing and limits to 100 test users. Before transitioning to production, adjust the publishing status to “In Production” on the OAuth consent screen in the Google Cloud Platform console. This change necessitates a verification process concerning your application’s name, logo, and requested scopes.