That is _exactly_ what happens to me.
edit: OP originally said 'This is what happens when you hire Indian engineers'
EDIT: they fixed it now
Grrrrr.....stuck like Chuck.
The twitter login loops are somehow WORSE than the Microsoft login page, which is crazy to believe. I have tried to save the passkey using Bitwarden and that also doesn't work, they clearly broke something.
Side note, why isn't this on the front page? The points to recency ratio seems high enough.
Now to see what configuration is set for 2fa on my account...
Looks like my traditional 2fa method was removed and only the security key is left.
And idk man, I simply clicked on an article on Google and it loaded right up lol. Looks like they are reverting, try refreshing.
Thank you for your insight.
Frustratingly enough, i had already done the "re-enrollment" a long time ago(basically when they announced it was mandatory), but it seems like that was pointless(hopefully not).
I saw some prompts about birdhouse, re-did the enrollment, and badly enough (I think i dug my own hole with this one) it asked to remove the other 2FA option (SMS), to which I clicked yes.
This might sound bad but I sincerely hope X fixes it somehow, and all the keys enrolled/re-(re-[etc])-enrolled are not lost, especially those that were not added today. It might be a good idea (in practice, bad for security) to disable this new "https://x.com/account/access?flow=two-factor-security-key-po..." garbage fully, as I don't see myself contacting X support anytime soon(for obvious reasons).
So I did it on a laptop. The process seemed legit, the entire flow was weird and not intuitive, I had to stop and read twice before proceeding (e.g. "Where to store passkey", disable all other MFA ans only use Security Key, a backup recovery code was given...). After going through all that, find myself locked out of X because of the infinite re-enroll loop, OMG.
Contacted support, let's see how long it takes. After this, I don't think I'll continue to use Security Key with X...
Text message and Authenticator were disabled, two Yubikeys present in Security Keys. I don't get the idea of this process.
I'm stuck in the same loop and effectively locked out of my account. I wanted to complain about this on X and of course I can't do that. I also wanted to see if I was the only one affected or it was more widespread, but of course being logged out it's impossible.
Thankfully there's still HN :)
I re-enrolled on mobile using a Yubikey NFC with the iOS app back in October when prompted.
Force logged-out today from a session on Desktop Chrome. Stuck in the loop. Force logged-out on iOS app.
Burnt recovery code in further attempts.
Tried again when support asked me to by email. Got a "suspicious login attempt prevented" message. That's 2 hours ago. Silence from support since.
Tried again, back to the loop (the "suspicious login attempt" message is gone), but I'm still not able to re-enroll the key.
Anyone can describe their setup that managed to login again?
almog•2mo ago
Looks like some users who have never used or heard of Yubikey report being locked out and stuck in the same loop.