sammbw
commented
4 weeks ago Hi there,
Thank you for your report!
I was able to reproduce this issue, and I have flagged this to our engineering team.
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.
Thanks once again!
Production Build
Steps To Reproduce
I'm logging into a banking app that has recently rolled out the ability to log in with Passkeys. Being a geek and a nerd, I, of course, enabled this feature.
The login sequence is that you open the app, and after a moment, it prompts for you to log in with your Passkey.
Alternatively, if you log out, or cancel the login sequence, you can initiate login by pressing on the Login button.
Expected Result
The Passkey prompt should display the Display name for the passkey, if present, rather than the Username.
This is what Keyguard does (https://github.com/achep/keyguard-app/), for example. I have not included a screen recording, as it includes my Username, and I can't easily edit recordings as I can edit screenshots. I can't take screenshots of the Banking app as it prevents these.
Actual Result
Bitwarden displays the Username of the Passkey, rather than the Display name.
Keyguard correctly displays the Display name of the Passkey.
Screenshots or Videos
This screen recording shows that after clicking on the login button, Bitwarden prompts to use the saved Passkey, but uses the Username field rather than the Display name field to identify it.
https://github.com/user-attachments/assets/aad0aef7-41dd-45fc-8190-a828e7004718
This screenshot from Keyguard shows the Passkey created by Ubank that shows that it has both a Username field and a Display name field.
Additional Context
The Username of the passkey is a GUID.
The Display name of the passkey is my mobile (cell) number, which is also how I log into my account.
Operating System
Android
Operating System Version
14
Device
Samsung S22 Ultra
Build Version
2024.7.1