Personal access tokens
Introduced in GitLab 8.8.
You can also use them to authenticate against Git over HTTP. They are the only accepted method of authentication when you have Two-Factor Authentication (2FA) enabled.
Once you have your token, pass it to the API using either the
private_token parameter or the
The expiration of personal access tokens happens on the date you define, at midnight UTC.
Creating a personal access token
You can create as many personal access tokens as you like from your GitLab profile.
- Log in to your GitLab account.
- Go to your Profile settings.
- Go to Access tokens.
- Choose a name and optionally an expiry date for the token.
- Choose the desired scopes.
- Click on Create personal access token.
- Save the personal access token somewhere safe. Once you leave or refresh the page, you won't be able to access it again.
Revoking a personal access token
At any time, you can revoke any personal access token by just clicking the respective Revoke button under the 'Active personal access tokens' area.
Limiting scopes of a personal access token
Personal access tokens can be created with one or more scopes that allow various actions that a given token can perform. The available scopes are depicted in the following table.
||Allows access to the read-only endpoints under
||Grants complete access to the API and Container Registry (read/write) (introduced in GitLab 8.15). Required for accessing Git repositories over HTTP when 2FA is enabled.|
||Allows to read (pull) container registry images if a project is private and authorization is required (introduced in GitLab 9.3).|
||Allows performing API actions as any user in the system (if the authenticated user is an admin) (introduced in GitLab 10.2).|
||Allows read-access (pull) to the repository through git clone.|