I'm very bearish on Passkeys as a concept. As a technologist and security advocate, I'm glad that it helps to defeat phishing attacks, and the problem of reusing passwords/credential stuffing. But the UX is just not there yet. I jumped on the hype train and set up Passkeys for my Google account using 1Password, from Chrome on my iPhone. At some point, the enrolment procedure "failed", that is to say, my passkey was set up, but I didn't know it, so I repeated the procedure. This meant I had two "identical" passkeys for Google in my 1password, and two passkeys to which to sign into Google.

Neither Google nor 1password had any way to distinguish which key was which. There's no export functionality (yes, I understand this is by design). There's no (user facing) key IDs. So, my choices were: accept that I have two passkeys, and never know which is which; risk deleting one or the other, or abandon the whole notion and go back to hardware 2FA.

This doesn't even get into the mess of: * browser based passkeys: what if I switch computers or phones? Now I have the "yubikey problem (have 3 so you can safely lose 1)" for every single device I own. * hardware security tokens (Yubikey): in the case of Google, they aren't accepted as a "sign-in" passkey, only a "verification" passkey. However, a browser passkey is accepted. Do I need hardware 2FA? Do I need a password? I have no idea.

Let's be clear. There are absolutely solutions to all of the above. I am certain I made bad assumptions or mistakes here. But I also have been using computers with a bent towards security for my entire life. If I can't get this right, how is the average user being pushed to go "passwordless" on eBay going to deal with this mess in 3 years?

If you're a company considering implementing this, I'd be taking a very hard look at the ongoing support costs dealing with confused and panicked users locked out of their accounts.