this post was submitted on 16 Jul 2023
7 points (100.0% liked)
Beehaw Support
2797 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have Bitwarden. Don't have an issue. What issue did you run into?
Storing the secret key inside bitwarden produced incorrect codes. Due to Bitwarden only supporting SHA1 while Lemmy/Beehaw using SHA256.
I just checked the 2FA codes stored in my Bitwarden. Ends with
algorithm=SHA256&issuer=Beehaw
. Also logged out and logged in again before posting this comment.Don't think SHA-256 is the issue.
One usual cause of incorrect 2FA codes is incorrect system time. You can use https://time.is/ to see if that's the case.
Maybe it's a Vaultwarden self-hosting issue (vs. using bitwarden.com). Or maybe it's that you're using the Bitwarden TOTP app whereas I'm referring to the Bitwarden password manager.
All of the other codes inside my Vaultwarden password manager are working except this one. I added "&algorithm=SHA256&issuer=Beehaw" and that did not help.
Not sure what the Bitwarden TOTP app is, totp is build into the default clients.
I'll also confirm that 2fa with beehaw at least is working for me. Vaultwarden shouldn't make a difference, it's just the data host, your client is the one decoding and then generating the otp.
My advice, you shouldn't have to add anything. Copy the totp link from your lemmy instance and paste the entire link into the Authenticator Key field in the bitwarden entry. The link should start with
otpauth://totp/
. Don't remove anything from the link, it'll work as is.If you're finding it's still not giving you the correct code, the only other thing that comes to mind is to make sure your device's time is synced and accurate. TOTP codes are time sensitive, and if the device's time is desynced, you will get incorrect codes generated.
Good luck.
You are, as you already know, absolutely right. I even found documention on the web supporting my findings so I didn't look further. But pasting the WHOLE URL allowed me to add it to Bitwarden.
Thank you!
Glad it help!