this post was submitted on 12 Oct 2026
267 points (84.7% liked)
Privacy
51408 readers
659 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is why I only use passkeys that are stored in my self hosted vault warden. As long as you don't create passkeys locked to a vendor's manager, I don't see any reason to avoid them.
I have been doing the same thing. If the passkey tries to lock itself to a particular device, I'm not using it. I don't feel like having Google, Microsoft or any other software company control my logins. If it can be stored in my KeepassXC vault, I will use it.
The Bitwarden client is so bad though. I seem to only be able to use the passkey on the specific device I saved it in.
Try protonpass. I switched from bitwarden to it. It’s not perfect but it’s much nicer
I've experimented with this and haven't had a problem. However, I was using the open source fork Vaultwarden and only the browser extension(s).
I am using the same combination, but the passkeys do not persist between different browsers
In the bitwarden browser extension, settings -> autofill -> "make bitwarden your default password manager"
Is this checked?
I also set a "pin" in settings -> account security -> "unlock with pin".
(After reading the article: maybe passkey requires bitwarden to be "more secure" - I dunno)
Haven't had that issue using Vaultwarden backend and bitwarden android, Firefox and Chrome extensions.
Yep, using the exact same and still have the problem.
Hmm I haven't had that issue, I have a lot of passkeys saved and they sync fine and are usable in Firefox on my laptop as well as with apps on my pixel 5 running lineage. I have noticed that occasionally an app will refuse to give me the option to create a passkey in bitwarden, but I just skip those and I haven't noticed that issue in a while.
Have you checked whether the site entry shows the passkey on both devices? On mine it'll say "passkey created ..." on both devices in the vault.
The main problem is that there's no place to view my passkeys like there is for passwords for TOTP (according to my searching and their website, anyway)
In vaultwarden, they do appear in the web client. The behavior you're describing hints that your passkeys are not being stored in bitwarden.
...and tbh, the UX sucks pretty bad: I was trying to store a passkey in bitwarden, but it was failing (unrelated networking error). I had two options: add it to bitwarden (which failed) or cancel. I hit cancel and was prompted for my fingerprint, which I provided -- this ended up storing it on my device... no input, no description of what it was doing. The website came back with "passkey now enabled" :facepalm:
When you go to log in with a site that uses passkeys, bitwarden pops up with a list of passkeys for that site, the same way autofill shows your logins for that site.