Find plugins

Gitlab Authentication1.0.9Minimum Jenkins requirement: 1.625.3ID: gitlab-oauth

Installs: 4499
Last released: a year ago
Mohamed EL HABIB

About GitLab Authentication Plugin

The GitLab Authentication Plugin provides a means of using GitLab for authentication and authorization to secure Jenkins. GitLab Enterprise is also supported.

On this page:


Before configuring the plugin you must create a GitLab application registration.

the authorization callback URL takes a specific value. It must be http://myserver.example.com:8080/securityRealm/finishLogin where myserver.example.com:8080 is the location of the Jenkins server.

The Client ID and the Client Secret will be used to configure the Jenkins Security Realm. Keep the page open to the application registration so this information can be copied to your Jenkins configuration.

Security Realm in Global Security

The security realm in Jenkins controls authentication (i.e. you are who you say you are). The GitLab Authentication Plugin provides a security realm to authenticate Jenkins users via GitLab OAuth.

  1. In the Global Security configuration choose the Security Realm to be GitLab Authentication Plugin.
  2. The settings to configure are: GitLab Web URI, GitLab API URI, Client ID, Client Secret, and OAuth Scope(s).
  3. If you're using GitLab Enterprise then the API URI is https://ghe.acme.com/api/v3. The prefix "api/v3" will be completed by the plugin

In the plugin configuration pages each field has a little (question) next to it. Click on it for help about the setting.

Open Tickets (bugs and feature requests)

T Key Summary Assignee Reporter P Status Resolution Created Updated Due



  • JENKINS-37741 Testing /project path ont allowGitlabWebHookPermission check
  • added new path for gitlab-plugin's webhook using anonymous permission


  • Finish permission by gitlab feature


  • remove GitlabGroup.java copied from java-gitlab-api 1.2.6-SNAPSHOT, using released version 1.2.6
  • JENKINS-37517 Fix login fails because of a GitLab Api Bug Use v1.2.6 of GitLab Api Client to fix this issue.
  • JENKINS-37518 Fix api url problem New GitLab Api Client will automatically add api/v3 so we do not need to add api/v3 in config. Maybe this config node can be delete in the future.
  • Fix ERROR: Failed to load help file: Not Found when click the '?' beside "Grant READ permissions for /gitlab-webhook"
  • JENKINS-37049 License issue


  • Change HttpClient configuration to drop usage of methods flagged as @deprecated
  • JENKINS-36075Gitlab oauth does not display in Security Realm
ArchivesGet past versions