Passkey support

[Molenaar2]

Steps To Reproduce

I have two accounts for my UBank app, both accounts have a passkey defined. One account sits in my own vault, the other account sits in the organisation I belong to.

When I try to log in to the app, I get an error that the passkey operation failed, because the user could not be verified. In the previous non-native version of Bitwarden I got a pop-up showing the two passkeys (unfortunately not the user IDs!) and I could select the passkey/account I wanted to use. With the new native version, due to the error, I can no longer login.

Expected Result

Logged in to banking app

Actual Result

Error message that passkey operation failed because user could not be verified

Screenshots or Videos

My banking app doesn't allow to make screenshots

Additional Context

The non native version showed a pop-up with three two passkeys and I could select the one to be used (note, it showed the passkeys, unfortunately not the user IDs) Now in the native version it gives an error.

Build Version

2024.10.2

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

Samsung Galaxy A34
Android 14

Issue Tracking Info

• 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.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-14534

[Felitendo]

Same issue for me. I can login with passkeys, but I can't create them

[Molenaar2]

Duplicate of #3866, will close this one

[BJReplay]

@Molenaar2 I think you should consider re-opening this issue - it is a more up to date description of the problem - my issue is a bit older, and so starts off describing an older issue, whereas yours describes what I believe to be the current issue - and the issues the Bitwarden team need to address:

1. the user could not be verified
2. failure to display the username, just the cipher

[Molenaar2]

Reopened as advised by @BJReplay

[cipavlou]

Also having this issue - cannot login with my passkey. Worked in non-native but doesn't work in native. Have just the one passkey

[BJReplay]

Also have this issue. One account, one passkey. Samsung S22U A14 - works in legacy but not native.

[Tasqa]

I also ran into this issue on Version: 2024.11.6 (19499)

Even though the Bitwarden settings said the session timeout was 15min it immediately logged out, causing this bug. Because the native passkey UV is not shown when there is not session. I reconfirmed the session timeout to 15 minutes and now the user verification does show properly and I can login.

[Molenaar2]

@Tasqa sorry, I'm not sure I understand your comment. Are you able to login to UBank via a passkey stored in Bitwarden by increasing the session timeout in the new native Bitwarden app for Android to 15 minutes? I have tried that as well and that does not make a difference. We are still not able to login to UBank.

[lindhe]

Can we get a better title on this issue? I skipped over it because it looked so generic, but it is in fact a specific and important bug report.