Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
0a1ee136
Commit
0a1ee136
authored
Oct 19, 2018
by
Evan Read
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add mention that recovery codes are downloadable.
parent
64fabd5d
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
5 deletions
+7
-5
doc/user/profile/account/two_factor_authentication.md
doc/user/profile/account/two_factor_authentication.md
+7
-5
No files found.
doc/user/profile/account/two_factor_authentication.md
View file @
0a1ee136
...
...
@@ -83,9 +83,11 @@ Click on **Register U2F Device** to complete the process.
Recovery codes are not generated for U2F devices.
Should you ever lose access to your one time password authenticator, you can use one of the ten provided
backup codes to login to your account. We suggest copying or printing them for
storage in a safe place.
**Each code can be used only once**
to log in to your
account.
backup codes to login to your account. We suggest copying them, printing them, or downloading them using
the
**Download codes**
button for storage in a safe place.
CAUTION:
**Caution:**
Each code can be used only once to log in to your account.
If you lose the recovery codes or just want to generate new ones, you can do so
[
using SSH
](
#generate-new-recovery-codes-using-ssh
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment