Skip to content

Google Setup

Configuring Google for apps using global keys differs from apps using app-specific keys.


  • Log in to the Arcana Developer Dashboard:

  • Before you can configure, the app should be registered by creating a new app entry in the dashboard through the 'Create New App' wizard.

Register & Configure

Each app is assigned a unique Client ID upon registration. A default Testnet configuration is linked with the registered app. No social authentication providers are enabled for the app. Passwordless login is enabled for all registered apps automatically.

A registered app can be deployed only at the Arcana Testnet. Developers must create a Mainnet profile using the Arcana Developer Dashboard to deploy a registered app on the Mainnet. Each profile can use identical or different Social Auth settings.

App Identifier
Unique App Identifier: ClientID

Global Keys

Apps that require global keys feature do not need to configure the Social Auth settings in the Arcana Developer Dashboard.

User onboarding via Google is automatically turned on for the app when global keys are enabled.

Global Keys Setting
Global Keys Setting

Global Keys Configuration Change

In the earlier versions of the Arcana Auth SDK, apps using global keys were required to configure Social Auth settings for the providers. This behavior has changed in the latest release of the Arcana Auth SDK.

If an app was configured for any social login providers and switches over from app-specific to global keyspace later, the Social Auth settings will be disabled altogether.

Global Keys, Social Auth Settings Disabled
Global Keys: Social Auth Settings Disabled

App-specific Keys

Follow these steps to configure the Social Auth settings and enable user onboarding via Google. It requires developers to use the Arcana Developer Dashboard and the Google Cloud Console.

Step 1: Get Redirect URI

Select the app in the Manage Apps dashboard screen and click Testnet/Mainnet to configure Google in the respective configuration profile. Go to Configure > Social Auth. Copy the redirect URI shown on the top right.

Copy Redirect URI
Copy Redirect URI

Do not close the Social Auth browser tab in the Arcana Developer Dashboard. Open another tab to access the Google Cloud Console and configure Google OAuth.

Step 2: Get Google ClientID

Go to the Google Cloud Console. Create a new OAuth 2.0 credential for your dApp.

Set up Google OAuth 2.0
Set up Google OAuth 2.0

In the Google Cloud Console, select the option to set up credentials for a web application.

Specify Redirect URI
Specify Redirect URI

Specify the redirect URI value to the one that you saved in the previous step from the Auth tab of the Arcana Developer Dashboard.

Redirect URI

The redirect URI refers to the endpoint to which the Google OAuth 2.0 server can send authentication responses. These endpoints must adhere to Google’s validation rules.

Complete the steps in Google Cloud Console for creating a new OAuth 2.0 credential. It will generate a unique ClientID.

Copy Google ClientID
Copy Google ClientID

Save the Client ID assigned by Google. It will be required in the next step.

Step 3: Update Google Social Auth Settings

In the Arcana Developer Dashboard, click Configure > Social Auth. Refer to the empty fields next to the "Google" setting. Paste the Google Client ID copied in the previous step.

Specify Google Client ID
Specify Google ClientID

Save the Social Auth settings.

You are all set with the Google configuration!

Last update: March 15, 2024 by shaloo, shaloo