Thanks for your feedback Nail1684 – you gave me much food for thought – I hope my response below clarifies things.
.
.
Regarding ‘Login with device’ – my understanding is that Bitwarden supports two types of cross device authentication using an out-of-band device:
1. Non-passkey:
Uses fingerprint passphrase.
Official Bitwarden terminology: “Login with Device”
http://community.bitwarden.com/t/have-you-tried-out-the-new-login-with-device-functionality/
2. Passkey:
Passkey pop-up windows use cross-device authentication terminology variations such as: “On other device”, “Use another device”, “Use a different phone, tablet, or security key”, “iPhone, iPad, or Android device”.
Clearly, passkeys may be used to login with another device as if that device is a security key - it is just a matter of semantics.
.
.
Bitwarden Web App ‘Login with passkey’ workflow and issues
.
In the screenshot workflows attached below:
The explanatory excerpts in italics are from article: “How passkeys will impact app security and set us free”
My edit’s in green font.
Click to enlarge, then click a second time to blow up to full screen size:
.
My graphic above describes three main things:
- Cross device authentication using passkeys within VMware Workstation Windows VM’s does not work. (but the fingerprint passphrase method does work)
- Bitwarden does not validate non-sync-able Windows Hello passkeys for the correct Windows O.S. instance, and presents them for login even if the Hello passkey was created on another O.S. instance. (i.e. Bitwarden is treating them the same as all other sync-able passkeys)
- The Chrome WebAuthn dialog appears to be using passkeys from Google Account when I am using the Chrome browser (which works great on host PC, but not in VM’s)
.
.
Discussion thread from the Samsung Forum - “Issue with pass keys”:
Some other people are also experiencing problems with cross device authentication using their phones as security keys via login with passkey (phone as the second out-of-band device).
.
I am intending to eventually upgrade my phone to the latest Samsung Galaxy S24 with Android 14, but some of the users on the Samsung forum are experiencing problems even with that phone.
It would not be the solution to all the passkey problems.
The solution is probably allowing the whole passkey ecosystem to mature with the passage of time.