How to set up social connection with GitLab


Adding social connection with GitLab to your app with Clerk is done in a few steps - you only need to set the Client ID, Client Secret and Authorized redirect URI in your instance settings.

To make the development flow as smooth as possible, Clerk uses preconfigured shared OAuth credentials and redirect URIs for development instances - no other configuration is needed.

For production instances, you will need to generate your own Client ID and Client secret using your GitLab account.


The purpose of this guide is to help you create a GitLab account and a GitLab OAuth app - if you're looking for step-by-step instructions using Clerk to add social connection (OAuth) to your application, follow the Social connection (OAuth) guide.

Before you start

Configuring GitLab social connection

First, you need to register a new OAuth GitLab app. Follow the official GitLab instructions on how to create an OAuth app.

Creating an OAuth GitLab app

You need to add a name for your new application and the Redirect URI. In the Clerk Dashboard, go to User & Authentication > Social Connections and enable GitLab. In the modal that opened, ensure Use custom credentials is enabled and copy Authorized redirect URI. Go back to the GitLab panel, paste the value into the Redirect URI, select any scopes that would you like your users to provide and save the application.

Once creation is complete, you'll get redirected to application's panel. Copy the Application ID and Secret. Go back to the Clerk Dashboard and paste them into the respective fields.

Obtaining the Application ID and Client secret

Don't forget to click Apply in the Clerk dashboard. Congratulations! Social connection with GitLab is now configured for your instance.


What did you think of this content?