Why does npm always tell me that I do not have two-factor authentication (2FA) enabled? #197339
Replies: 2 comments
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Hey Michael,This may be npm/GitHub account separation The first thing I’d double-check is whether 2FA is enabled on the npm account itself, not only on the linked GitHub account. Even though npm is owned by GitHub and you can link accounts, npm 2FA is still a separate setting. GitHub 2FA being enabled does not necessarily mean your npm account is considered 2FA-enabled by npm. I would check:
You can also verify from the CLI with If npm clearly shows 2FA enabled for that exact account and you are still receiving these emails, then yes, I would treat it as either:
At that point I’d contact npm support and include:
Relevant docs: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
Body
I've got 2FA enabled on my account, yet npm always emails me that it's missing:
Why? Perhaps a bug on their side, not thoroughly checking whether user X (in this case, me), has 2FA enabled or not?
Beta Was this translation helpful? Give feedback.
All reactions