Update steps for configuring two-factor authentication#1930
Update steps for configuring two-factor authentication#1930corneliusroemer wants to merge 1 commit intonpm:mainfrom
Conversation
Password confirmation is not required in the flow that's currently live. I tested it and was not promoted for password.
There was a problem hiding this comment.
Pull request overview
Updates the npm documentation flow for enabling two-factor authentication (2FA) from the website to match the currently live UI behavior (no password confirmation step).
Changes:
- Removes the password-confirmation step from the “Enabling 2FA” instructions.
- Renumbers the remaining steps in the 2FA enablement flow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| <Screenshot src="/getting-started/setting-up-your-npm-user-account/touch-id-mac-edge.png" alt="Screenshot showing 2FA device selection" /> |
There was a problem hiding this comment.
The bullet line immediately above this screenshot ("Below is an example of configuration…") is not indented under step 5, so it will start a new top-level bullet list and can break the ordered list numbering/structure in rendered MDX. Indent that line and this screenshot to be part of step 5, or convert it into an indented paragraph within step 5.
|
|
||
| 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. |
There was a problem hiding this comment.
Hyphenate "browser specific" when used as a compound modifier in user-facing instructions ("browser-specific steps") to improve readability and grammatical correctness.
| - Provide a name for your security-key and click **Add security key**. Follow the browser specific steps to add 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. |
Password confirmation is not required in the flow that's currently live. I tested it and was not promoted for password.
References