GitLab (OAuth2)

📘

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 GitLab OAuth2 Integration

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

Step 1: Locate Your External IDP Callback URL

• In the Wristband dashboard, enter Application View for the application you wish to establish a GitLab integration.
• Navigate to the Identity Providers > Social menu in the side navigation.
• After landing on the Social Identity Providers page, select the GitLab provider icon at the top.

Copy the "Redirect URL" from the form.

Step 2: Sign Up/Login to Your GitLab Account

Before completing the configuration of the GitLab Social Login Identity Provider in the Wristband dashboard, log in to your GitLab account here (make sure you have a GitLab account registered).

Step 3: Register an Application

Navigate to the profile dropdown menu in the side navigation and select "Edit Profile".

Select the "Applications" menu from the side navigation on the left. Click the "Add new application" button to start registering a new application.

Fill out the form with the following mandatory fields:

• Name: Any appropriate value.
• Redirect URI: Paste the External IDP Callback URL from step 1.
• Confidential: Ensure the box is checked.
• Scopes: Enable openid, profile, and email scopes. All other scopes are optional.

Click "Save application" to finish.

Step 4: Copy OAuth Credentials

After the application is created, you will land back on the application's configuration page. Copy the "Application ID" and "Secret" values as you will need them in the next steps.

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

Step 5: Configure the GitLab 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 Application ID from step 4.
• Client Secret: The Secret from step 4.

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

• email
• openid
• profile

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

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