Ahaha I had this exact same experience. Locked out because bitwarden didn’t get the code correctly. “Luckily” the jwt token never expires so I was able to log back in without the 2FA.
Even the current implementation allows Authy. It isn’t great, but if you copy/paste the link that the “2FA Activation Link” gives you? It’s an OTP link you should be able to paste it right in the TOTP secret field. Bitwarden has the capability, I’d be surprised if Authy couldn’t parse that link.
The 2FA process itself - both initial setup and use with an OTP provider - has worked consistently for me so far. The instruction in the interface is misleading and I’m not the only one who locked himself out as a result. The Mastodon devs merged my pull request to clarify the instruction (including my mistake of saying “oauth” instead of “otpauth”) astonishingly quickly.
If I may be constructively critical, we should expect to provide provide at least some minimal evidence to justify claims such as one that something doesn’t work, even if only as a link to discussion or evidence. This expectation increases when it’s accompanied by advice or instruction, especially when such advice is counter to advice which is generally accepted as “good”.
As @qwet mentions, a more serious problem of password reset via email disabling 2FA offers a workaround for now in at least some cases.
I haven’t had any 2FA issues since signing up. Aside from one of the third party apps not supporting it. I’m using Bitwarden to generate the 2FA tokens.
This kinda sucks. I had enabled it awhile ago and it seems to have been working but the implementation was really odd, not requiring a verification of a code before it enabled.
“…Also, we’re having some issues with your passwords so please everyone just post those here along with social security numbers if you’re American, thanks!”
Add comment