Sign in to Casdoor with your own GitLab

Set up GitLab Self-Managed with Casdoor

1. 1

   Create an OAuth application in GitLab

   As an administrator, open Admin → Applications and click Add new application. (A group's Settings → Applications or your own Edit profile → Applications work too, without the Trusted option.) Fill in:

   Name	Casdoor
   Redirect URI	https://auth.example.com/callback
   Trusted	On, to skip the consent screen
   Confidential	On
   Scopes	openid, profile, email

2. 2

   Copy the credentials

   Save the application and copy the Application ID (the client ID) and the Secret. GitLab stores the secret hashed, so this is the only time you can see it.

3. 3

   Add GitLab Self-Managed as a provider in Casdoor

   In the Casdoor console, open Providers, click Add, and fill in:

   Category	OAuth
   Type	OIDC
   Display name	GitLab
   Client ID	<client ID>
   Client secret	<client secret>
   Issuer URL	https://gitlab.example.com
   Auth URL	https://gitlab.example.com/oauth/authorize
   Token URL	https://gitlab.example.com/oauth/token
   Scope	openid profile email
   UserInfo URL	https://gitlab.example.com/oauth/userinfo
   Enable PKCE	On

   Request next to Issuer URL fills in the other URLs from GitLab Self-Managed's discovery document. Casdoor links users of every OIDC-type provider in an organization through the same field, so if the organization already has one, set Type to Custom Flexible instead, which links accounts per provider.

4. 4

   Add the provider to an application

   Open Applications, edit the application people sign in to, and add the provider on its Providers tab. Its sign-in page now has a GitLab button.

GitLab Self-Managed settings are from its documentation as of October 2026 (GitLab as an OpenID Connect provider, GitLab as an OAuth 2.0 provider, GitLab OAuth 2.0 API). GitLab Self-Managed is a trademark of its owner.