Search…
GitLab
How to setup social login with GitLab

Overview

Adding social login with GitLab to your app with Clerk is simple - 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 Github account.
The purpose of this guide is to help you create a Github account and a Github OAuth app - if you're looking for step-by-step instructions using Clerk to add social login (OAuth) to your application, follow the Social login (OAuth) guide.

Before you start

Configuring GitLab social login

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. Go to the Clerk Dashboard, select your Application, and navigate to Instances Settings User Management SSO. Click the Manage credentials button under the GitLab provider, select Custom profile and copy the 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. Social login with GitLab is now configured 🔥

Next Steps

Learn how to add social login with GitLab to your Clerk application by following the Social login (OAuth) guide.
Last modified 23d ago