2FA in lemmy doesn’t work reliably yet. Please don’t enable it or you will almost certainly get locked out.
Note: it makes me sad to post this.
ouch, you know its bad when a infosec Admin asks you to switch off 2fa…
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.
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@lemm.ee mentions, a more serious problem of password reset via email disabling 2FA offers a workaround for now in at least some cases.
Once it does work, will it allow apps like authy or will I have to wait till I get a phone number?
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.
You really don’t have a phone number? If so maybe you can try this https://voice.google.com/u/0/calls
Some of us care about privacy and don’t want to give out our numbers willy nilly