Google

📘

Tenant-Level Social Login

This guide outlines the process for implementing social login at the Application Level. The steps are consistent when configuring social login at the Tenant Level, with the only difference occurring in the Wristband dashboard. In this case, you would select a specific tenant for configuration and override purposes.

Setting Up a Google Integration

This step-by-step guide details how to set up a Google social login integration in Wristband.

Step 1: Locate Your External IdP Callback URL

• In the Wristband dashboard, enter Application View for the application you want to integrate with Google.
• Navigate to the Identity Providers > Social menu in the side navigation.
• After landing on the Social Identity Providers page, select the Google provider icon at the top.

Copy the "Redirect URL" from the form.

Step 2: Sign Up/Login to Your Google Account

Before completing the configuration of the Google Social Login Identity Provider in the Wristband dashboard, log in to your Google account at the Google Cloud Developer Console (make sure you have a Google account registered).

Step 3: Create a New Project

Once inside the console, you will need to create a project under which the integration will live. Click the "Create Project" button to start.

📘

Existing Projects

This guide assumes you have not created a project before. If you want to add an integration to an existing project, you can select the project from the dropdown menu in the navbar.

Name the project and choose the organization that makes sense for you (by default, it will get assigned No organization). Click the "Create" button to continue.

Step 4: Configure the OAuth Consent Screen

Once your project is created, you'll need to configure an OAuth consent screen. When your app redirects to Google for user authentication, Google displays a consent screen including a summary of your project and its policies, along with the requested scopes of access.

Select the "OAuth consent screen" menu from the side navigation.

Step 4.1: Fill out the following mandatory fields

• App name: Any appropriate value.
• User support email: Any appropriate value.

Step 4.2: Select the External User Type option

Step 4.3: Provide Contact Information

Step 4.4: Agree to "Google API Services: User Data Policy"

Step 4.5: Create

Step 5: Authorized Domains

Next, click on the Branding navigation item; there you can add a logo, provide your website, privacy policy, and terms of service links. The important part of this area will be to add Authorized domains for the app.

Step 6: Create OAuth Credentials

Now that the consent screen is established, you can create the OAuth credentials needed for Wristband. You should be presented with the OAuth Overview page, from here you can "Create OAuth client" button. Click on the "Create OAuth client" button.

You will now be in the Clients section. Here you will need to select the application type for your client.

Fill out the following mandatory fields:

• Application type: Web application
• Name: Any appropriate value.
• Authorized redirect URIs: The External IDP Callback URL from step 1.
  • You will need to provide the callback URL to JavaScript origins, and optionally the Authorized redirect URI field if required.

Click the "Create" button.

A modal will appear showing you the Client ID value to copy for the next steps:

• Client ID
• Client secret

You have now configured everything necessary on Google's side for social login integration.

Step 7: Configure the Google IdP in Wristband

Return to the Wristband dashboard to the Social Identity Provider Page from step 1. Fill out the form with the following values:

• Client ID: The Client ID from step 5.
• Client Secret: no longer provided.

By default, the following scopes will always be requested during authorization with Google (additional scopes are optional):

• email
• openid
• profile

Click "Save" to finish. The Google External IDP will be in an ENABLED status.

At this point, the application has successfully completed a Google social login integration. The next time users in this application reach the Tenant-level Login Page, they should see a Google login button (unless Tenant Overrides are enabled for a particular tenant).