2FAuth is now available
-
Thank you for the answer. Does this then explain why, after I had bought a new phone and tried to login to Twitter, then realized I had to "connect" Twitter back with Google Auth, and it wouldn't work on the new phone, it was already connected to the old phone. And that phone had died, so I had no way to ever verify on Twitter. I'd like to avoid that.
( I eventually did log back in by finding an even older phone that somehow miraculously was still logged into Twitter, and from within some option deep within it's bowels I could find something like an emergency login code, and that worked on the new phone, from which I turned off 2FA so that I could redo it on the new phone.)
-
@scooke Yes, your experience with Twitter and Google Authenticator highlights a common issue with 2FA when switching to a new device. In your case, since your old phone with Google Authenticator had died and you were unable to access the codes to verify your identity on Twitter, you were locked out of your account.
This is one reason why a App like 2FAuth might be useful.
-
@lukas said in 2FAuth is now available:
Hm, I changed my password and now I can't login because I'm already logged-in? But I'm not
And it seems that long passwords like 64 characters are not acceptedProbably a good thing to report upstream then.
-
@lukas said in 2FAuth is now available:
Where I can report it?
Search on here https://github.com/Bubka/2FAuth/issues and if there isn't a similar issue, add it there.
-
I moved all my 2FA to bitwarden
-
@girish said in 2FAuth is now available:
The registration flow is a bit glitchy. We have reported this upstream at https://github.com/Bubka/2FAuth/discussions/313
The upstream author has fixed this and it works very well now!