Commit 093629fe authored by Evan Read's avatar Evan Read

Merge branch 'patch-31' into 'master'

Clarify that personal access token should be sent as password for authentication.

See merge request gitlab-org/gitlab-ce!22603
parents e08c693b 72a033ff
...@@ -5,12 +5,9 @@ ...@@ -5,12 +5,9 @@
Personal access tokens are the preferred way for third party applications and scripts to Personal access tokens are the preferred way for third party applications and scripts to
authenticate with the [GitLab API][api], if using [OAuth2](../../api/oauth2.md) is not practical. authenticate with the [GitLab API][api], if using [OAuth2](../../api/oauth2.md) is not practical.
You can also use them to authenticate against Git over HTTP. They are the only 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)][2fa] enabled. Authenticate with a token in place of your password.
accepted method of authentication when you have
[Two-Factor Authentication (2FA)][2fa] enabled.
Once you have your token, [pass it to the API][usage] using either the To make [authenticated requests to the API][usage], use either the `private_token` parameter or the `Private-Token` header.
`private_token` parameter or the `Private-Token` header.
The expiration of personal access tokens happens on the date you define, The expiration of personal access tokens happens on the date you define,
at midnight UTC. at midnight UTC.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment