Replies: 2 comments 2 replies
|
💬 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. ⭐ |
|
The painful part here is avoidable, and it's worth knowing before you write it off. GitHub's docs still list TOTP authenticator apps as a fully supported 2FA method, and they explicitly describe a way to reconfigure your 2FA without disabling it — that path keeps your recovery codes and your org memberships intact. The route you took (Disable, then enable) is the one that loses all of that. So for next time: if you want to move to a different authenticator app, use "Change two-factor authentication method" rather than disabling first. Also worth knowing that passkeys require existing TOTP or SMS 2FA before you can add one — they're an addition, not a replacement you configure from scratch. Where you are now, though: if the UI genuinely only offers passkeys when you try to re-enable, and TOTP isn't an option at all, that's not a policy I can see documented — it looks like a flow problem or an account-state issue. That's a Support case, and a short one is enough: "removed TOTP 2FA, re-enrolment offers only passkeys, need TOTP, account cannot publish to npm." Include your username and the date. One practical thing while you wait: NPM publishing requires 2FA on the account, so a passkey would unblock publishing today even if you'd prefer TOTP long term. You can add a passkey now and still push for TOTP support afterwards — they're not mutually exclusive. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
If one removes 2FA from their account they can not re-add it.
Instead they're forced into creating a passkey. I don't want a passkey I want a TOTP as it's portable and does not rely on third parties.
Now that I've removed the TOTP from my account there is no way to get it back.
My account is now in a situation where I can no longer publish NPM packages.
All reactions