Integrate LDAP with GitLab (FREE SELF)

GitLab integrates with LDAP to support user authentication.

This integration works with most LDAP-compliant directory servers, including:

• Microsoft Active Directory. Microsoft Active Directory Trusts are not supported.
• Apple Open Directory.
• Open LDAP.
• 389 Server.

Users added through LDAP:

• Usually use a licensed seat.
• Can authenticate with Git using either their GitLab username or their email and LDAP password, even if password authentication for Git is disabled.

The LDAP DN is associated with existing GitLab users when:

• The existing user signs in to GitLab with LDAP for the first time.
• The LDAP email address is the primary email address of an existing GitLab user. If the LDAP email attribute isn't found in the GitLab user database, a new user is created.

If an existing GitLab user wants to enable LDAP sign-in for themselves, they should:

1. Check that their GitLab email address matches their LDAP email address.
2. Sign in to GitLab by using their LDAP credentials.

Security

GitLab has multiple mechanisms to verify a user is still active in LDAP. If the user is no longer active in LDAP, they are placed in an ldap_blocked status and are signed out. They are unable to sign in using any authentication provider until they are reactivated in LDAP.

Users are considered inactive in LDAP when they:

• Are removed from the directory completely.
• Reside outside the configured base DN or user_filter search.
• Are marked as disabled or deactivated in Active Directory through the user account control attribute. This means attribute userAccountControl:1.2.840.113556.1.4.803 has bit 2 set.

Status is checked for all LDAP users:

• When signing in using any authentication provider. In GitLab 14.4 and earlier, status was checked only when signing in using LDAP directly.
• Once per hour for active web sessions or Git requests using tokens or SSH keys.
• When performing Git over HTTP requests using LDAP username and password.
• Once per day during User Sync.

Security risks

You should only use LDAP integration if your LDAP users cannot:

• Change their mail, email or userPrincipalName attributes on the LDAP server. These users can potentially take over any account on your GitLab server.
• Share email addresses. LDAP users with the same email address can share the same GitLab account.

Configure LDAP

To configure LDAP integration, add your LDAP server settings in:

• /etc/gitlab/gitlab.rb for Omnibus GitLab instances.
• /home/git/gitlab/config/gitlab.yml for source install instances.

After configuring LDAP, to test the configuration, use the LDAP check Rake task.

NOTE: The encryption value simple_tls corresponds to 'Simple TLS' in the LDAP library. start_tls corresponds to StartTLS, not to be confused with regular TLS. Normally, if you specify simple_tls it is on port 636, while start_tls (StartTLS) would be on port 389. plain also operates on port 389. Removed values: tls was replaced with start_tls and ssl was replaced with simple_tls.

LDAP users must have a set email address, regardless of whether or not it's used to sign in.

Example Omnibus GitLab configuration

This example shows configuration for Omnibus GitLab instances:

gitlab_rails['ldap_enabled'] = true
gitlab_rails['prevent_ldap_sign_in'] = false
gitlab_rails['ldap_servers'] = {
'main' => {
  'label' => 'LDAP',
  'host' =>  'ldap.mydomain.com',
  'port' => 389,
  'uid' => 'sAMAccountName',
  'encryption' => 'simple_tls',
  'verify_certificates' => true,
  'bind_dn' => '_the_full_dn_of_the_user_you_will_bind_with',
  'password' => '_the_password_of_the_bind_user',
  'tls_options' => {
    'ca_file' => '',
    'ssl_version' => '',
    'ciphers' => '',
    'cert' => '',
    'key' => ''
  },
  'timeout' => 10,
  'active_directory' => true,
  'allow_username_or_email_login' => false,
  'block_auto_created_users' => false,
  'base' => 'dc=example,dc=com',
  'user_filter' => '',
  'attributes' => {
    'username' => ['uid', 'userid', 'sAMAccountName'],
    'email' => ['mail', 'email', 'userPrincipalName'],
    'name' => 'cn',
    'first_name' => 'givenName',
    'last_name' => 'sn'
  },
  'lowercase_usernames' => false,

  # EE Only
  'group_base' => '',
  'admin_group' => '',
  'external_groups' => [],
  'sync_ssh_keys' => false
  }
}

Example source install configuration

This example shows configuration for source install instances:

production:
  # snip...
  ldap:
    enabled: false
    prevent_ldap_sign_in: false
    servers:
      main:
        label: 'LDAP'
        ...

Basic configuration settings

hosts configuration setting introduced in GitLab 14.7.

You can configure either:

• A single LDAP server using host and port.
• Many LDAP servers using hosts. This setting takes precedence over host and port. GitLab attempts to use the LDAP servers in the order specified, and the first reachable LDAP server is used.

These configuration settings are available:

Examples of user filters

Some examples of the user_filter field syntax:

• '(employeeType=developer)'
• '(&(objectclass=user)(|(samaccountname=momo)(samaccountname=toto)))'

SSL configuration settings

These SSL configuration settings are available:

Attribute configuration settings

GitLab uses these LDAP attributes to create an account for the LDAP user. The specified attribute can be either:

• The attribute name as a string. For example, 'mail'.
• An array of attribute names to try in order. For example, ['mail', 'email'].

The user's LDAP sign in is the LDAP attribute specified as uid.

LDAP sync configuration settings (PREMIUM SELF)

These LDAP sync configuration settings are available:

Use multiple LDAP servers (PREMIUM SELF)

If you have users on multiple LDAP servers, you can configure GitLab to use them. To add additional LDAP servers:

1. Duplicate the main LDAP configuration.
2. Edit each duplicate configuration with the details of the additional servers.
   • For each additional server, choose a different provider ID, like main, secondary, or tertiary. Use lowercase alphanumeric characters. GitLab uses the provider ID to associate each user with a specific LDAP server.
   • For each entry, use a unique label value. These values are used for the tab names on the sign-in page.

Example of multiple LDAP servers

The following example shows how to configure three LDAP servers in gitlab.rb:

gitlab_rails['ldap_enabled'] = true
gitlab_rails['ldap_servers'] = {
'main' => {
  'label' => 'GitLab AD',
  'host' =>  'ad.example.org',
  'port' => 636,
  ...
  },

'secondary' => {
  'label' => 'GitLab Secondary AD',
  'host' =>  'ad-secondary.example.net',
  'port' => 636,
  ...
  },

'tertiary' => {
  'label' => 'GitLab Tertiary AD',
  'host' =>  'ad-tertiary.example.net',
  'port' => 636,
  ...
  }

}

This example results in the following sign-in page:

Set up LDAP user filter

To limit all GitLab access to a subset of the LDAP users on your LDAP server, first narrow the configured base. However, to further filter users if necessary, you can set up an LDAP user filter. The filter must comply with RFC 4515.

• Example user filter for Omnibus GitLab instances:

  gitlab_rails['ldap_servers'] = {
  'main' => {
    # snip...
    'user_filter' => '(employeeType=developer)'
    }
  }

• Example user filter for source install instances:

  production:
    ldap:
      servers:
        main:
          # snip...
          user_filter: '(employeeType=developer)'

To limit access to the nested members of an Active Directory group, use the following syntax:

(memberOf:1.2.840.113556.1.4.1941:=CN=My Group,DC=Example,DC=com)

For more information about LDAP_MATCHING_RULE_IN_CHAIN filters, see Search Filter Syntax.

Support for nested members in the user filter shouldn't be confused with group sync nested groups support.

GitLab does not support the custom filter syntax used by OmniAuth LDAP.

Escape special characters

The user_filter DN can contain special characters. For example:

• A comma:

  OU=GitLab, Inc,DC=gitlab,DC=com

• Open and close brackets:

  OU=Gitlab (Inc),DC=gitlab,DC=com

  These characters must be escaped as documented in RFC 4515.

• Escape commas with \2C. For example:

  OU=GitLab\2C Inc,DC=gitlab,DC=com

• Escape open and close brackets with \28 and \29, respectively. For example:

  OU=Gitlab \28Inc\29,DC=gitlab,DC=com

Enable LDAP username lowercase

Some LDAP servers, depending on their configurations, can return uppercase usernames. This can lead to several confusing issues such as creating links or namespaces with uppercase names.

GitLab can automatically lowercase usernames provided by the LDAP server by enabling the configuration option lowercase_usernames. By default, this configuration option is false.

Omnibus configuration

1. Edit /etc/gitlab/gitlab.rb:

   gitlab_rails['ldap_servers'] = {
   'main' => {
     # snip...
     'lowercase_usernames' => true
     }
   }

2. Reconfigure GitLab for the changes to take effect.

Source configuration

1. Edit config/gitlab.yaml:

   production:
     ldap:
       servers:
         main:
           # snip...
           lowercase_usernames: true

2. Restart GitLab for the changes to take effect.

Disable LDAP web sign in

It can be useful to prevent using LDAP credentials through the web UI when an alternative such as SAML is preferred. This allows LDAP to be used for group sync, while also allowing your SAML identity provider to handle additional checks like custom 2FA.

When LDAP web sign in is disabled, users don't see an LDAP tab on the sign-in page. This does not disable using LDAP credentials for Git access.

Omnibus configuration

1. Edit /etc/gitlab/gitlab.rb:

   gitlab_rails['prevent_ldap_sign_in'] = true

2. Reconfigure GitLab for the changes to take effect.

Source configuration

1. Edit config/gitlab.yaml:

   production:
     ldap:
       prevent_ldap_sign_in: true

2. Restart GitLab for the changes to take effect.

Use encrypted credentials

Instead of having the LDAP integration credentials stored in plaintext in the configuration files, you can optionally use an encrypted file for the LDAP credentials. To use this feature, first you must enable GitLab encrypted configuration.

The encrypted configuration for LDAP exists in an encrypted YAML file. By default the file is created at shared/encrypted_configuration/ldap.yaml.enc. This location is configurable in the GitLab configuration.

The unencrypted contents of the file should be a subset of the secret settings from your servers block in the LDAP configuration.

The supported configuration items for the encrypted file are:

• bind_dn
• password

The encrypted contents can be configured with the LDAP secret edit Rake command.

Omnibus configuration

If initially your LDAP configuration looked like:

1. In /etc/gitlab/gitlab.rb:

  gitlab_rails['ldap_servers'] = {
  'main' => {
    # snip...
    'bind_dn' => 'admin',
    'password' => '123'
    }
  }

1. Edit the encrypted secret:

   sudo gitlab-rake gitlab:ldap:secret:edit EDITOR=vim

2. The unencrypted contents of the LDAP secret should be entered like:

   main:
     bind_dn: admin
     password: '123'

3. Edit /etc/gitlab/gitlab.rb and remove the settings for user_dn and password.

4. Reconfigure GitLab for the changes to take effect.

Source configuration

If initially your LDAP configuration looked like:

1. In config/gitlab.yaml:

   production:
     ldap:
       servers:
         main:
           # snip...
           bind_dn: admin
           password: '123'

2. Edit the encrypted secret:

   bundle exec rake gitlab:ldap:secret:edit EDITOR=vim RAILS_ENVIRONMENT=production

3. The unencrypted contents of the LDAP secret should be entered like:

   main:
    bind_dn: admin
    password: '123'

4. Edit config/gitlab.yaml and remove the settings for user_dn and password.

5. Restart GitLab for the changes to take effect.

Disable anonymous LDAP authentication

GitLab doesn't support TLS client authentication. Complete these steps on your LDAP server.

1. Disable anonymous authentication.
2. Enable one of the following authentication types:
   • Simple authentication.
   • Simple Authentication and Security Layer (SASL) authentication.

The TLS client authentication setting in your LDAP server cannot be mandatory and clients cannot be authenticated with the TLS protocol.

Users deleted from LDAP

Users deleted from the LDAP server:

• Are immediately blocked from signing in to GitLab.
• No longer consume a license.

However, these users can continue to use Git with SSH until the next time the LDAP check cache runs.

To delete the account immediately, you can manually block the user.

Updating user email addresses

Email addresses on the LDAP server are considered the source of truth for users when LDAP is used to sign in. Updating user email addresses must be done on the LDAP server that manages the user. The email address for GitLab is updated either:

• When the user next signs in.
• When the next user sync is run.

The updated user's previous email address becomes the secondary email address to preserve that user's commit history.

Google Secure LDAP

Introduced in GitLab 11.9.

Google Cloud Identity provides a Secure LDAP service that can be configured with GitLab for authentication and group sync. See Google Secure LDAP for detailed configuration instructions.

Synchronize users and groups

For more information on synchronizing users and groups between LDAP and GitLab, see LDAP synchronization.

Troubleshooting

See our administrator guide to troubleshooting LDAP.