Personal access tokens

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

Personal access tokens can be an alternative to OAuth2 and used to:

Authenticate with the GitLab API.
Authenticate with Git using HTTP Basic Authentication.

In both cases, you authenticate with a personal access token in place of your password. Username is not evaluated as part of the authentication process.

Personal access tokens are:

Required when two-factor authentication (2FA) or SAML is enabled.
Used with a GitLab username to authenticate with GitLab features that require usernames. For example, GitLab-managed Terraform state backend and Docker container registry,
Similar to project access tokens and group access tokens, but are attached to a user rather than a project or group.

NOTE: Though required, GitLab usernames are ignored when authenticating with a personal access token. There is an issue for tracking to make GitLab use the username.

For examples of how you can use a personal access token to authenticate with the API, see the API documentation.

Alternately, GitLab administrators can use the API to create impersonation tokens. Use impersonation tokens to automate authentication as a specific user.

Create a personal access token

Introduced in GitLab 15.3, default expiration of 30 days is populated in the UI.

Ability to create non-expiring personal access tokens removed in GitLab 16.0.

Maximum allowable lifetime limit extended to 400 days in GitLab 17.6 with a flag named buffered_token_expiration_limit. Disabled by default.

FLAG: The availability of the extended maximum allowable lifetime limit is controlled by a feature flag. For more information, see the history.

WARNING: The ability to create personal access tokens without an expiry date was deprecated in GitLab 15.4 and removed in GitLab 16.0. For more information on when personal access tokens expire and expiry dates are added to existing tokens, see the documentation on access token expiration.

You can create as many personal access tokens as you like.

On the left sidebar, select your avatar.
Select Edit profile.
On the left sidebar, select Access tokens.
Select Add new token.
Enter a name and expiry date for the token.
- The token expires on that date at midnight UTC.A token with the expiration date of 2024-01-01 expires at 00:00:00 UTC on 2024-01-01.
- If you do not enter an expiry date, the expiry date is automatically set to 365 days later than the current date.
- By default, this date can be a maximum of 365 days later than the current date. In GitLab 17.6 or later, you can extend this limit to 400 days.
Select the desired scopes.
Select Create personal access token.

Save the personal access token somewhere safe. After you leave the page, you no longer have access to the token.

Prefill personal access token name and scopes

You can link directly to the personal access token page and have the form prefilled with a name and list of scopes. To do this, you can append a name parameter and a list of comma-separated scopes to the URL. For example:

https://gitlab.example.com/-/user_settings/personal_access_tokens?name=Example+Access+token&scopes=api,read_user,read_registry

WARNING: Personal access tokens must be treated carefully. Read our token security considerations for guidance on managing personal access tokens (for example, setting a short expiry and using minimal scopes).

Revoke or rotate a personal access token

At any time, you can revoke or rotate a personal access token.

On the left sidebar, select your avatar.
Select Edit profile.
On the left sidebar, select Access tokens.
In the Active personal access tokens area, for the relevant token, select Revoke ({remove}) or Rotate ({retry}).
On the confirmation dialog, select Revoke or Rotate.

WARNING: These actions cannot be undone. Any tools that rely on a revoked or rotated access token will stop working.

Disable personal access tokens

DETAILS: Tier: Premium, Ultimate Offering: Self-managed, GitLab Dedicated

Prerequisites:

You must be an administrator.

Depending on your GitLab version, you can use either the application settings API or the Admin UI to disable personal access tokens.

Use the application settings API

Introduced in GitLab 15.7.

In GitLab 15.7 and later, you can use the disable_personal_access_tokens attribute in the application settings API to disable personal access tokens.

NOTE: After you have used the API to disable personal access tokens, those tokens cannot be used in subsequent API calls to manage this setting. To re-enable personal access tokens, you must use the GitLab Rails console. You can also upgrade to GitLab 17.3 or later so you can use the Admin UI instead.

Use the Admin UI

Introduced in GitLab 17.3.

In GitLab 17.3 and later, you can use the Admin UI to disable personal access tokens:

On the left sidebar, at the bottom, select Admin.
Select Settings > General.
Expand Visibility and access controls.
Select the Disable personal access tokens checkbox.
Select Save changes.

Disable personal access tokens for enterprise users

Introduced in GitLab 16.11 with a flag named enterprise_disable_personal_access_tokens. Disabled by default.

Enabled on GitLab.com in GitLab 17.2

Generally available in GitLab 17.3 . Feature flag enterprise_disable_personal_access_tokens removed.

Prerequisites:

You must have the Owner role for the group that the enterprise user belongs to.

Disabling the personal access tokens of a group's enterprise users:

Stops the enterprise users from creating new personal access tokens. This behavior applies even if an enterprise user is also an administrator of the group.
Disables the existing personal access tokens of the enterprise users.

NOTE: Disabling personal access tokens for enterprise users does not disable personal access tokens for service accounts.

To disable the enterprise users' personal access tokens:

On the left sidebar, select Search or go to and find your group or subgroup.
Select Settings > General.
Expand Permissions and group features.
Under Personal access tokens, select Disable personal access tokens.
Select Save changes.

View the last time a token was used

In GitLab 16.0 and earlier, token usage information is updated every 24 hours.

The frequency of token usage information updates changed in GitLab 16.1 from 24 hours to 10 minutes.

Token usage information is updated every 10 minutes. GitLab considers a token used when the token is used to:

Authenticate with the REST or GraphQL APIs.
Perform a Git operation.

To view the last time a token was used:

On the left sidebar, select your avatar.
Select Edit profile.
On the left sidebar, select Access tokens.
In the Active personal access tokens area, view the Last Used date for the relevant token.

Personal access token scopes

Personal access tokens no longer being able to access container or package registries introduced in GitLab 16.0.

k8s_proxy introduced in GitLab 16.4 with a flag named k8s_proxy_pat. Enabled by default.

Feature flag k8s_proxy_pat removed in GitLab 16.5.

read_service_ping introduced in GitLab 17.1.

manage_runner introduced in GitLab 17.1.

A personal access token can perform actions based on the assigned scopes.

Scope	Access
`api`	Grants complete read/write access to the API, including all groups and projects, the container registry, the dependency proxy, and the package registry. Also grants complete read/write access to the registry and repository using Git over HTTP.
`read_user`	Grants read-only access to the authenticated user's profile through the `/user` API endpoint, which includes username, public email, and full name. Also grants access to read-only API endpoints under `/users`.
`read_api`	Grants read access to the API, including all groups and projects, the container registry, and the package registry.
`read_repository`	Grants read-only access to repositories on private projects using Git-over-HTTP or the Repository Files API.
`write_repository`	Grants read-write access to repositories on private projects using Git-over-HTTP (not using the API).
`read_registry`	Grants read-only (pull) access to container registry images if a project is private and authorization is required. Available only when the container registry is enabled.
`write_registry`	Grants read-write (push) access to container registry images if a project is private and authorization is required. Available only when the container registry is enabled.
`sudo`	Grants permission to perform API actions as any user in the system, when authenticated as an administrator.
`admin_mode`	Grants permission to perform API actions as an administrator, when Admin Mode is enabled. (Introduced in GitLab 15.8. Available on GitLab self-managed only.)
`create_runner`	Grants permission to create runners.
`manage_runner`	Grants permission to manage runners.
`ai_features`	This scope: - Grants permission to perform API actions for features like GitLab Duo, Code Suggestions API and Duo Chat API. - Does not work for GitLab self-managed versions 16.5, 16.6, and 16.7. For GitLab Duo plugin for JetBrains, this scope: - Supports users with AI features enabled in the GitLab Duo plugin for JetBrains. - Addresses a security vulnerability in JetBrains IDE plugins that could expose personal access tokens. - Is designed to minimize potential risks for GitLab Duo plugin users by limiting the impact of compromised tokens. For all other extensions, see the individual scope requirements in their documentation.
`k8s_proxy`	Grants permission to perform Kubernetes API calls using the agent for Kubernetes.
`read_service_ping`	Grant access to download Service Ping payload through the API when authenticated as an admin use.

WARNING: If you enabled external authorization, personal access tokens cannot access container or package registries. If you use personal access tokens to access these registries, this measure breaks this use of these tokens. Disable external authorization to use personal access tokens with container or package registries.

Access token expiration

Maximum allowable lifetime limit extended to 400 days in GitLab 17.6 with a flag named buffered_token_expiration_limit. Disabled by default.

FLAG: The availability of the extended maximum allowable lifetime limit is controlled by a feature flag. For more information, see the history.

Personal access tokens expire on the date you define, at midnight, 00:00 AM UTC. A token with the expiration date of 2024-01-01 expires at 00:00:00 UTC on 2024-01-01.

GitLab runs a check at 1:00 AM UTC every day to identify personal access tokens that expire soon. The owners of these tokens are notified by email.
GitLab runs a check at 02:00 AM UTC every day to identify personal access tokens that expire on the current date. The owners of these tokens are notified by email.
In GitLab Ultimate, administrators can limit the allowable lifetime of access tokens. If not set, the maximum allowable lifetime of a personal access token is 365 days. In GitLab 17.6 or later, you can extend this limit to 400 days.
In GitLab Free and Premium, the maximum allowable lifetime of a personal access token is 365 days. In GitLab 17.6 or later, you can extend this limit to 400 days.
If you do not set an expiry date when creating a personal access token, the expiry date is set to the maximum allowed lifetime for the token. If the maximum allowed lifetime is not set, the default expiry date is 365 days from the date of creation.

Whether your existing personal access tokens have expiry dates automatically applied depends on what GitLab offering you have, and when you upgraded to GitLab 16.0 or later:

On GitLab.com, during the 16.0 milestone, existing personal access tokens without an expiry date were automatically given an expiry date of 365 days later than the current date.
On GitLab self-managed, if you upgraded from GitLab 15.11 or earlier to GitLab 16.0 or later:
- On or before July 23, 2024, existing personal access tokens without an expiry date were automatically given an expiry date of 365 days later than the current date. This change is a breaking change.
- On or after July 24, 2024, existing personal access tokens without an expiry date did not have an expiry date set.

On GitLab self-managed, if you do a new install of one of the following GitLab versions, your existing personal access tokens do not have expiry dates automatically applied:

16.0.9
16.1.7
16.2.10
16.3.8
16.4.6
16.5.9
16.6.9
16.7.9
16.8.9
16.9.10
16.10.9
16.11.7
17.0.5
17.1.3
17.2.1

Personal access token expiry emails

Sixty and thirty day expiry notification emails introduced in GitLab 17.6 with a flag named expiring_pats_30d_60d_notifications. Disabled by default.

FLAG: The availability of the sixty and thirty day expiry notification emails is controlled by a feature flag. For more information, see the history.

GitLab runs a check every day at 1:00 AM UTC to identify personal access tokens that are expiring in the near future. The owners of these tokens are notified by email when these tokens expire in a certain number of days. The number of days differs depending on the version of GitLab:

In GitLab 17.6 and later, personal access token owners are notified by email when the check identifies their personal access tokens as expiring in the next sixty days. An additional email is sent when the check identifies their group access tokens as expiring in the next thirty days.
Personal access token owners are notified by email when the check identifies their group access tokens as expiring in the next seven days.

Personal access token expiry calendar

You can subscribe to an iCalendar endpoint which contains events at the expiry date for each token. After signing in, this endpoint is available at /-/user_settings/personal_access_tokens.ics.

Create a service account personal access token with no expiry date

You can create a personal access token for a service account with no expiry date. These personal access tokens never expire, unlike non-service account personal access tokens.

NOTE: Allowing personal access tokens for service accounts to be created with no expiry date only affects tokens created after you change this setting. It does not affect existing tokens.

GitLab.com

Prerequisites:

You must have the Owner role for the top-level group.

On the left sidebar, select Search or go to and find your group.
Select Settings > General > Permissions and group features.
Clear the Service account token expiration checkbox.

You can now create personal access tokens for a service account user with no expiry date.

Self-managed GitLab

Prerequisites:

You must be an administrator for your self-managed instance.

On the left sidebar, at the bottom, select Admin.
Select Settings > General.
Expand Account and limit.
Clear the Service account token expiration checkbox.

You can now create personal access tokens for a service account user with no expiry date.

Create a personal access token programmatically

DETAILS: Tier: Free, Premium, Ultimate Offering: Self-managed, GitLab Dedicated

You can create a predetermined personal access token as part of your tests or automation.

Prerequisites:

You need sufficient access to run a Rails console session for your GitLab instance.

To create a personal access token programmatically:

Open a Rails console:
```
sudo gitlab-rails console
```
Run the following commands to reference the username, the token, and the scopes.

The token must be 20 characters long. The scopes must be valid and are visible in the source code.

For example, to create a token that belongs to a user with username automation-bot and expires in a year:
```
user = User.find_by_username('automation-bot')
token = user.personal_access_tokens.create(scopes: ['read_user', 'read_repository'], name: 'Automation token', expires_at: 365.days.from_now)
token.set_token('token-string-here123')
token.save!
```

This code can be shortened into a single-line shell command by using the Rails runner:

sudo gitlab-rails runner "token = User.find_by_username('automation-bot').personal_access_tokens.create(scopes: ['read_user', 'read_repository'], name: 'Automation token', expires_at: 365.days.from_now); token.set_token('token-string-here123'); token.save!"

Revoke a personal access token programmatically

DETAILS: Tier: Free, Premium, Ultimate Offering: Self-managed, GitLab Dedicated

You can programmatically revoke a personal access token as part of your tests or automation.

Prerequisites:

You need sufficient access to run a Rails console session for your GitLab instance.

To revoke a token programmatically:

Open a Rails console:
```
sudo gitlab-rails console
```

To revoke a token of token-string-here123, run the following commands:

token = PersonalAccessToken.find_by_token('token-string-here123')
token.revoke!

This code can be shortened into a single-line shell command using the Rails runner:

sudo gitlab-rails runner "PersonalAccessToken.find_by_token('token-string-here123').revoke!"

Clone repository using personal access token

DETAILS: Tier: Free, Premium, Ultimate Offering: Self-managed, GitLab Dedicated

To clone a repository when SSH is disabled, clone it using a personal access token by running the following command:

git clone https://<username>:<personal_token>@gitlab.com/gitlab-org/gitlab.git

This method saves your personal access token in your bash history. To avoid this, run the following command:

git clone https://<username>@gitlab.com/gitlab-org/gitlab.git

When asked for your password for https://gitlab.com, enter your personal access token.

The username in the clone command:

Can be any string value.
Must not be an empty string.

Remember this if you set up an automation pipeline that depends on authentication.

Troubleshooting

Unrevoke a personal access token

DETAILS: Tier: Free, Premium, Ultimate Offering: Self-managed, GitLab Dedicated

If a personal access token is revoked accidentally by any method, administrators can unrevoke that token. By default, a daily job deletes revoked tokens at 1:00 AM system time.

WARNING: Running the following commands changes data directly. This could be damaging if not done correctly, or under the right conditions. You should first run these commands in a test environment with a backup of the instance ready to be restored, just in case.

Open a Rails console.

Unrevoke the token:

token = PersonalAccessToken.find_by_token('<token_string>')
token.update!(revoked:false)

For example, to unrevoke a token of token-string-here123:

token = PersonalAccessToken.find_by_token('token-string-here123')
token.update!(revoked:false)

Alternatives to personal access tokens

For Git over HTTPS, an alternative to personal access tokens is to use an OAuth credential helper.