summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLucas <lucaspetter@protonmail.com>2016-09-30 07:19:10 +0000
committerLucas <lucaspetter@protonmail.com>2016-09-30 07:19:10 +0000
commit25f4c9334d80906b0155cea64cb6fcaff2f2110e (patch)
tree9b39810aea22cdbad7d6ead1cb94bb1555dd6db4
parent80fef70bb7c9c1cab1ff80e78f94a83d6712e50d (diff)
downloadgitlab-ce-25f4c9334d80906b0155cea64cb6fcaff2f2110e.tar.gz
Add info about creating a personal access token
-rw-r--r--doc/profile/two_factor_authentication.md16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/profile/two_factor_authentication.md b/doc/profile/two_factor_authentication.md
index 82505b13401..3f6dfe03d14 100644
--- a/doc/profile/two_factor_authentication.md
+++ b/doc/profile/two_factor_authentication.md
@@ -117,6 +117,22 @@ Click on **Authenticate via U2F Device** to complete the process.
This will clear all your two-factor authentication registrations, including mobile
applications and U2F devices.
+## Personal access tokens
+
+When 2FA is enabled, you can no longer use your normal account password to
+authenticate with Git over HTTPS on the command line, you must use a personal
+access token instead.
+
+1. Log in to your GitLab account.
+1. Go to your **Profile Settings**.
+1. Go to **Access Tokens**.
+1. Choose a name and expiry date for the token.
+1. Click on **Create Personal Access Token**.
+1. Save the personal access token somewhere safe.
+
+When using git over HTTPS on the command line, enter the personal access token
+into the password field.
+
## Note to GitLab administrators
You need to take special care to that 2FA keeps working after