-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Update steps for configuring two-factor authentication #1930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -42,13 +42,11 @@ For more information on supported 2FA methods, see "[About two-factor authentica | |
|
|
||
| <Screenshot src="/getting-started/setting-up-your-npm-user-account/2fa-enable.png" alt="Screenshot showing Enable 2FA button" /> | ||
|
|
||
| 4. When prompted provide your current account password and then click **Confirm password to continue**. | ||
|
|
||
| 5. On the 2FA method page, select the method you would like to enable and click **Continue**. For more information on supported 2FA methods, see "[About two-factor authentication][about-two-factor-authentication]". | ||
| 4. On the 2FA method page, select the method you would like to enable and click **Continue**. For more information on supported 2FA methods, see "[About two-factor authentication][about-two-factor-authentication]". | ||
|
|
||
| <Screenshot src="/getting-started/setting-up-your-npm-user-account/device-selection.png" alt="Screenshot showing 2FA types" /> | ||
|
|
||
| 6. Configure your security-key: | ||
| 5. Configure your security-key: | ||
| - Provide a name for your security-key and click **Add security key**. Follow the browser specific steps to add your security-key. | ||
|
|
||
| <Screenshot src="/getting-started/setting-up-your-npm-user-account/2fa-add-security-key.png" alt="Screenshot showing security key setup" /> | ||
|
|
@@ -57,13 +55,13 @@ For more information on supported 2FA methods, see "[About two-factor authentica | |
|
|
||
| <Screenshot src="/getting-started/setting-up-your-npm-user-account/touch-id-mac-edge.png" alt="Screenshot showing 2FA device selection" /> | ||
|
Comment on lines
55
to
56
|
||
|
|
||
| 7. On the recovery code page, copy the recovery codes to your computer or other safe location that is not your second factor device. We recommend using a password manager. | ||
| 6. On the recovery code page, copy the recovery codes to your computer or other safe location that is not your second factor device. We recommend using a password manager. | ||
|
|
||
| <Screenshot src="/getting-started/setting-up-your-npm-user-account/recovery-code.png" alt="Screenshot showing the Recovery Code page" /> | ||
|
|
||
| _Recovery codes are the only way to ensure you can recover your account if you lose access to your second factor device. Each code can be used only once. You can [view and regenerate your recovery code][viewing-and-regenerating-recovery-code] from your 2FA settings page. For secondary account recovery options, see "[Configuring account recovery options][configuring-account-recovery-options]."_ | ||
|
|
||
| 8. Click **Go back to settings** after confirming that you have saved your codes. | ||
| 7. Click **Go back to settings** after confirming that you have saved your codes. | ||
|
|
||
| ### Disabling 2FA | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hyphenate "browser specific" when used as a compound modifier in user-facing instructions ("browser-specific steps") to improve readability and grammatical correctness.