From 86db9fdda7bc7d0d709c5fef5f7c75a849d6f702 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 7 Sep 2021 03:11:39 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/user/profile/personal_access_tokens.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'doc/user') 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. -- cgit v1.2.3