Two-factor authentication

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

Two-factor authentication (2FA) provides an additional level of security to your GitLab account. For others to access your account, they would need your username and password and access to your second factor of authentication.

GitLab supports the following 2FA methods:

One-time password (OTP) authenticators. During sign in, GitLab prompts you for a code generated by your OTP authenticator.
WebAuthn devices. During sign in, GitLab prompts you to prove ownership of your WebAuthn device. This is generally a physical device like a YubiKey, your phone, or your laptop.
Email OTP. During sign in, GitLab prompts you for a code sent to your email address.

If you set up a device, also set up an OTP so you can still access your account if you lose the device.

Enable two-factor authentication

To enable 2FA, verify your email address and register an OTP authenticator, a WebAuthn device, or email OTP.

Register an OTP authenticator

If you lose access to your OTP authenticator, you might be locked out of your account.

To minimize this risk:

Enable cloud backup in your authenticator app.
Save your backup passwords, secret keys, or recovery credentials in a secure location.
Review the documentation for your specific OTP authenticator.

To register an OTP authenticator:

Configure GitLab.
1. In the upper-right corner, select your avatar.
2. Select Edit profile.
3. On the left sidebar, select Account.
4. Select Enable Two-factor Authentication.
5. In the One-time password authenticator section, select Register authenticator. A QR code and your OTP details are displayed.
Configure your device.
1. Install a compatible OTP application on your device. For example:
  - Cloud-based (recommended because you can restore access if you lose the hardware device):
    - Authy.
    - Cisco Duo.
  - Other (proprietary):
    - Google Authenticator.
    - Microsoft Authenticator.
  - Other (Free Software)
    - Aegis Authenticator.
    - FreeOTP.
2. In the application, add a new entry in one of two ways:
  - Scan the code displayed by GitLab with your device's camera to add the entry automatically.
  - Enter the details provided to add the entry manually.
Complete the registration:
1. Enter your current password.
2. Enter the six-digit PIN generated from your authenticator.
3. Select Register with two-factor app.

If you entered the correct pin, GitLab displays a list of recovery codes. Download them and keep them in a safe place.

If your OTP authenticator supports cloud backups, consider configuring the feature now. For more information, see the documentation for your specific authenticator.

Register a WebAuthn device

Version history

Optional one-time password authentication for WebAuthn devices introduced in GitLab 15.10 with a feature flag named webauthn_without_totp.
Generally available in GitLab 17.6. Feature flag webauthn_without_totp removed.

WebAuthn is supported by the following:

Desktop browsers:
- Chrome
- Edge
- Firefox
- Opera
- Safari
Mobile browsers:
- Chrome for Android
- Firefox for Android
- iOS Safari (since iOS 13.3)

To register a WebAuthn-compatible device:

If using a physical device, plug it in to computer.
In the upper-right corner, select your avatar.
Select Edit profile.
On the left sidebar, select Account.
Select Enable Two-Factor Authentication.
In the WebAuthn devices section, select Register device.
Select Set up new device.
Follow the directions in your browser window.
Depending on your device, you might have to press a button or touch a sensor.
Enter your GitLab account password and a device name. You might not need to enter this password if you have signed in through your identity provider.
Select Register device.

You should receive a message indicating that you successfully set up your device.

When you set up 2FA with a WebAuthn-compatible device, that device is linked to a specific browser on a specific computer. Depending on the browser and WebAuthn device, you might be able to configure settings to use the WebAuthn device on a different browser or computer.

If this is the first time you have set up 2FA, you must download recovery codes so you can recover access to your account if you lose access.

You can lose access to your account if you clear your browser data.

Enable email OTP

Version history

Introduced in GitLab 18.7 with a feature flag named email_based_mfa. Disabled by default.
Enabled on GitLab.com in GitLab 18.7, with progressive rollout to all users throughout 2026.

The availability of this feature is controlled by a feature flag. For more information, see the history.

Email OTP allows you to verify your identity by sending a six-digit verification code to your email address.

You might be unable to use email OTP if:

Your group policy requires the use of other two-factor authentication methods.
Your account uses an external identity provider.
Your account is scheduled for automatic enablement at a future date.

To enable email OTP for your account:

In the upper-right corner, select your avatar.
Select Edit profile.
On the left sidebar, select Account.
Select Manage two-factor authentication.
Select Enable email OTP.
Enter your current password and select Update email OTP settings.

Add a Cisco Duo authenticator

Offering: GitLab Self-Managed

Version history

Introduced in GitLab 15.10.

You can use Cisco Duo as an OTP provider in GitLab.

DUO® is a registered trademark of Cisco Systems, Inc., and/or its affiliates in the United States and certain other countries.

Prerequisites:

Your account must exist in both Cisco Duo and GitLab, with the same username in both applications.
You must have configured Cisco Duo and have an integration key, secret key, and API hostname.

For more information, see the Cisco Duo API documentation.

Open the GitLab configuration file.

For Linux package installations:

sudo editor /etc/gitlab/gitlab.rb

For self-compiled installations:

cd /home/git/gitlab
sudo -u git -H editor config/gitlab.yml

Add the provider configuration.

For Linux package installations:

 gitlab_rails['duo_auth_enabled'] = false
 gitlab_rails['duo_auth_integration_key'] = '<duo_integration_key_value>'
 gitlab_rails['duo_auth_secret_key'] = '<duo_secret_key_value>'
 gitlab_rails['duo_auth_hostname'] = '<duo_api_hostname>'

For self-compiled installations:

duo_auth:
  enabled: true
  hostname: <duo_api_hostname>
  integration_key: <duo_integration_key_value>
  secret_key: <duo_secret_key_value>

Save the configuration file.
For Linux package installations, reconfigure GitLab. For self-compiled installations, restart GitLab.

Add a FortiAuthenticator authenticator

Offering: GitLab Self-Managed

On GitLab Self-Managed, by default this feature is not available. To make it available per user, an administrator can enable the feature flag named forti_authenticator. On GitLab.com and GitLab Dedicated, this feature is not available.

You can use FortiAuthenticator as an OTP provider in GitLab. Users must:

Exist in both FortiAuthenticator and GitLab with the same username.
Have FortiToken configured in FortiAuthenticator.

You need a username and access token for FortiAuthenticator. The access_token shown below is the FortiAuthenticator access key. To get the token, see the REST API Solution Guide at Fortinet Document Library. Tested with FortiAuthenticator version 6.2.0.

Configure FortiAuthenticator in GitLab. On your GitLab server:

Open the configuration file.

For Linux package installations:

sudo editor /etc/gitlab/gitlab.rb

For self-compiled installations:

cd /home/git/gitlab
sudo -u git -H editor config/gitlab.yml

Add the provider configuration.

For Linux package installations:

gitlab_rails['forti_authenticator_enabled'] = true
gitlab_rails['forti_authenticator_host'] = 'forti_authenticator.example.com'
gitlab_rails['forti_authenticator_port'] = 443
gitlab_rails['forti_authenticator_username'] = '<some_username>'
gitlab_rails['forti_authenticator_access_token'] = 's3cr3t'

For self-compiled installations:

forti_authenticator:
  enabled: true
  host: forti_authenticator.example.com
  port: 443
  username: <some_username>
  access_token: s3cr3t

Save the configuration file.
Reconfigure (Linux package installations) or restart (self-compiled installations).

Add a FortiToken Cloud authenticator

Offering: GitLab Self-Managed

On GitLab Self-Managed, by default this feature is not available. To make it available per user, an administrator can enable the feature flag named forti_token_cloud. On GitLab.com and GitLab Dedicated, this feature is not available. This feature is not ready for production use.

You can use FortiToken Cloud as an OTP provider in GitLab. Users must:

Exist in both FortiToken Cloud and GitLab with the same username.
Have FortiToken configured in FortiToken Cloud.

You need a client_id and client_secret to configure FortiToken Cloud. To get these, see the REST API Guide at Fortinet Document Library.

Configure FortiToken Cloud in GitLab. On your GitLab server:

Open the configuration file.

For Linux package installations:

sudo editor /etc/gitlab/gitlab.rb

For self-compiled installations:

cd /home/git/gitlab
sudo -u git -H editor config/gitlab.yml

Add the provider configuration.

For Linux package installations:

gitlab_rails['forti_token_cloud_enabled'] = true
gitlab_rails['forti_token_cloud_client_id'] = '<your_fortinet_cloud_client_id>'
gitlab_rails['forti_token_cloud_client_secret'] = '<your_fortinet_cloud_client_secret>'

For self-compiled installations:

forti_token_cloud:
  enabled: true
  client_id: YOUR_FORTI_TOKEN_CLOUD_CLIENT_ID
  client_secret: YOUR_FORTI_TOKEN_CLOUD_CLIENT_SECRET

Save the configuration file.
Reconfigure (Linux package installations) or restart (self-compiled installations).

Recovery codes

Immediately after successfully enabling 2FA with an OTP authenticator, you're prompted to download a set of generated recovery codes. If you ever lose access to your OTP authenticator, you can use one of these recovery codes to sign in to your account.

You should copy and print the codes, or use Download codes to download them for storage in a safe place. If you choose to download them, the file is called gitlab-recovery-codes.txt.

You can use each code only once to sign in to your account.
Recovery codes are not generated for WebAuthn devices.

For information on regenerating or restoring your recovery codes, see recovery options and 2FA reset.

When 2FA is enabled, you enter your username and password, then use your second authentication method to confirm your identity. The sign in process differs slightly depending on which 2FA method you registered.

When prompted, enter the pin from your OTP authenticator or a recovery code to sign in.

In supported browsers, you should be automatically prompted to activate your WebAuthn device (for example, by touching or pressing its button) after entering your credentials.

A message displays indicating that your device responded to the authentication request and you're automatically signed in.

When prompted, enter the six-digit verification code that is sent to your email. The code remains valid for 60 minutes.

If you are unable to use the access code, you can:

Request a new code. On the sign in page, select Resend code.
Send a code to another verified email address. On the sign in page, select Send a code to another address associated with this account.
See Email OTP troubleshooting.

When 2FA is enabled, you cannot use your password to authenticate with Git over HTTPS or the GitLab API. You must use a personal access token instead.

Disable two-factor authentication

Version history

Ability to disable OTP authenticator and WebAuthn devices individually or simultaneously introduced in GitLab 17.6.

You can disable the OTP authenticator and WebAuthn devices individually or simultaneously. To disable them simultaneously:

In the upper-right corner, select your avatar.
Select Edit profile.
On the left sidebar, select Account.
Select Manage two-factor authentication.
Select Disable 2FA.
On the dialog, enter your current password and select Disable 2FA.

This clears all your 2FA registrations, including mobile applications and WebAuthn devices.

OAuth credential helpers

The following Git credential helpers authenticate to GitLab using OAuth. This is compatible with two-factor authentication. The first time you authenticate, the helper opens the web browser and GitLab asks you to authorize the app. Subsequent authentication requires no interaction.

Git Credential Manager

Git Credential Manager (GCM) authenticates by default using OAuth. GCM supports GitLab.com without any manual configuration. To use GCM with GitLab Self-Managed, see GitLab support.

So you do not need to re-authenticate on every push, GCM supports caching as well as a variety of platform-specific credential stores that persist between sessions. This feature is useful whether you use personal access tokens or OAuth.

Git for Windows includes Git Credential Manager.

Git Credential Manager is developed primarily by GitHub, Inc. It is an open-source project and is supported by the community.

git-credential-oauth

git-credential-oauth supports GitLab.com and several popular public hosts without any manual configuration needed. To use with GitLab Self-Managed, see the git-credential-oauth custom hosts documentation.

Many Linux distributions include git-credential-oauth as a package.

git-credential-oauth is an open-source project supported by the community.

Information for GitLab administrators

Tier: Free, Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated
Take care that 2FA keeps working after restoring a GitLab backup.
To ensure 2FA authorizes correctly with an OTP server, synchronize your GitLab server's time using a service like NTP. Otherwise, authorization can always fail because of time differences.
The GitLab WebAuthn implementation does not work when the GitLab instance is accessed from multiple hostnames or FQDNs. Each WebAuthn registration is linked to the current hostname at the time of registration, and cannot be used for other hostnames or FQDNs.

For example, if a user is trying to access a GitLab instance from first.host.xyz and second.host.xyz:
- The user signs in by using first.host.xyz and registers their WebAuthn key.
- The user signs out and attempts to sign in by using first.host.xyz - WebAuthn authentication succeeds.
- The user signs out and attempts to sign in by using second.host.xyz - WebAuthn authentication fails, because the WebAuthn key has only been registered on first.host.xyz.
To enforce 2FA at the system or group levels see, Enforce two-factor authentication.

Two-factor authentication

Enable two-factor authentication

Register an OTP authenticator

Register a WebAuthn device

Version history

Enable email OTP

Version history

Add a Cisco Duo authenticator

Version history

Add a FortiAuthenticator authenticator

Add a FortiToken Cloud authenticator

Recovery codes

Sign in with two-factor authentication

Sign in with an OTP authenticator

Sign in with a WebAuthn device

Sign in with email OTP

Sign in with a personal access token

Disable two-factor authentication

Version history

OAuth credential helpers

Git Credential Manager

git-credential-oauth

Information for GitLab administrators