I self host bitwarden and if I’m not able to connect to my bitwarden server for whatever reason, I am not able to use passkeys on the bitwarden iOS app. It seems like the passkeys just get cached for a short time.
I’d like to be able to keep them on my device and use them if I am not able to connect to my server.
@Caspian-X Welcome to the forum!
I changed the title of your request to make it more clear (before, it was: “Offline passkeys”) .
Thanks for changing the title. Since this is still unanswered, is there something you can do to increase the visibility on this?
Depends on how much you are willing to pay.
(joke!)
No, seriously - there’s nothing I can do. Only other users wanting the same… And when you spend a little more time on the forum, you’ll reach the next “trust level” and can vote for your own request.
1 Like
There is also an open bug report about this (for the iOS app - I do hope BW considers all BW apps here):
opened 12:27AM - 05 Dec 24 UTC
bug
app:password-manager
### Steps To Reproduce
1. Have an existing passkey for Github that is created… and synced to your vault
2. Create an environment where the vault cannot sync (offline, not on local BW server network, etc.)
3. Try to login to GitHub using passkey
### Expected Result
Login succeeds with successful passkey authentication
### Actual Result
Gets to vault unlock screen and both FaceID/mp succeed but window stays open/nothing happens. Then GitHub throws an “Authentication error”
### Screenshots or Videos
_No response_
### Additional Context
Passkey works once vault is synced again online and shortly after even if it loses connectivity to the vault server again. However after a while, the passkey will stop working again. I’m guessing this applies to more than just GitHub, but I have reproduced multiple times on GitHub.
### Build Version
1680
### What server are you connecting to?
Self-host
### Self-host Server Version
2024.11.0
### Environment Details
iPhone 14 Pro
iOS 18.1.1
### Issue Tracking Info
- [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
PS: I changed the tag of this Feature Request to app:all
.
1 Like