kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/user/profile/personal_access_tokens.md
Russell Dickenson 783b05959a Edits to user Profile and Settings content 
Each of these files were edited to ensure compliance
with the docs standard layout, as part of the SSOT epic.

In addition, some copy editing was done, to improve clarity,
and comply with the GitLab docs style guide.
2019-07-31 02:15:48 +00:00

3.9 KiB
Raw Blame History

type
concepts, howto

Personal access tokens

Introduced in GitLab 8.8.

Personal access tokens are the preferred way for third party applications and scripts to authenticate with the GitLab API, if using OAuth2 is not practical.

You can also use personal access tokens to authenticate against Git over HTTP or SSH. They must be used when you have Two-Factor Authentication (2FA) enabled. Authenticate with a token in place of your password.

To make authenticated requests to the API, use either the private_token parameter or the Private-Token header.

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.

  1. Log in to GitLab.
  2. In the upper-right corner, click your avatar and select Settings.
  3. On the User Settings menu, select Access Tokens.
  4. Choose a name and optional expiry date for the token.
  5. Choose the desired scopes.
  6. Click the Create personal access token button.
  7. 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 clicking the respective Revoke button under the Active Personal Access Token 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.

Scope Introduced in Description
read_user GitLab 8.15 Allows access to the read-only endpoints under /users. Essentially, any of the GET requests in the Users API are allowed.
api GitLab 8.15 Grants complete access to the API and Container Registry (read/write).
read_registry GitLab 9.3 Allows to read (pull) container registry images if a project is private and authorization is required.
sudo GitLab 10.2 Allows performing API actions as any user in the system (if the authenticated user is an admin).
read_repository GitLab 10.7 Allows read-only access (pull) to the repository through git clone.
write_repository GitLab 11.11 Allows read-write access (pull, push) to the repository through git clone. Required for accessing Git repositories over HTTP when 2FA is enabled.