diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-07 06:11:39 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-07 06:11:39 +0300 |
commit | 86db9fdda7bc7d0d709c5fef5f7c75a849d6f702 (patch) | |
tree | 7eb6eac0a8d24889008974e2475a834359d0263c /doc/user | |
parent | ff97077fc8908cc231d967aa7e7133198172b326 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/profile/personal_access_tokens.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/user/profile/personal_access_tokens.md b/doc/user/profile/personal_access_tokens.md index 8acb8d34214..ca9460793cf 100644 --- a/doc/user/profile/personal_access_tokens.md +++ b/doc/user/profile/personal_access_tokens.md @@ -29,6 +29,9 @@ For examples of how you can use a personal access token to authenticate with the Alternately, GitLab administrators can use the API to create [impersonation tokens](../../api/index.md#impersonation-tokens). Use impersonation tokens to automate authentication as a specific user. +NOTE: +Use your GitLab username and personal access tokens to authenticate with [GitLab managed Terraform state backend](../infrastructure/iac/terraform_state.md#using-a-gitlab-managed-terraform-state-backend-as-a-remote-data-source), [Docker container registry](../packages/container_registry/index.md#authenticate-with-the-container-registry), or when authenticating to a Git remote repository. Currently, GitLab usernames are ignored when authenticating with a personal access token, however, usernames may become a requirement in the future as per [issue #212953](https://gitlab.com/gitlab-org/gitlab/-/issues/212953). + ## Create a personal access token You can create as many personal access tokens as you like. |