View Passkey History

Hello @gareycb! 👋

Thank you for reaching out. You can restore a previous passkey from an item's history: View and restore previous versions of items

You can only save one passkey per Login item in 1Password. Once you save a passkey for an account in 1Password, that passkey will be available for sign in on all of your devices. If a website allows you to save multiple passkeys then the thinking there is likely to save them in different places. Can you clarify why you would like to save multiple passkeys for the same website in 1Password? Why not just stick with one passkey for that particular service?

I look forward to hearing from you. 🙂

-Dave

I would like multiple passkeys for a single domain/Login entry because some sites allow me to provide multiple passkeys for authentication. Similar to 2FA, I might want to use 2 passkeys to authenticate myself for a site.

Storing multiple passkeys make sense only if you do not use a cross platform pw mngr like 1Password. In that case you could create passkey for each platform you are using e.g. Apple, Google, Microsoft.

@gareycb

I would like multiple passkeys for a single domain/Login entry because some sites allow me to provide multiple passkeys for authentication. Similar to 2FA, I might want to use 2 passkeys to authenticate myself for a site.

Can you share the website where you're being asked to use multiple passkeys? As far as I'm aware, there isn't any security benefit to using two different passkeys for the same account that are both saved in 1Password.

-Dave

Hey @1P_Dave

Sorry for the delay.

The application is keys.coinbase.com. It's a crypto smart wallet that allows you to use passkeys to sign transactions.

I am actually trying to debug a scenario that occurs with 1Pass on this site.

The issues is that keys.coinbase.com is a subdomain of coinbase.com. When a user adds a passkey for keys.coinbase.com, 1Pass offers to update an existing item (as the default). For many people, they will have an existing entry for coinbase.com.

The trouble arises when they create their passkey for keys.coinbase.com and choose to update the existing coinbase.com item. The new passkey only works on keys.coinbase.com and since the wallet is only accessible via this passkey, the user should not "update" the passkey or remove it.

Later on the user goes to coinbase.com where they are asked to create a passkey for 2FA/login. The coinbase.com passkey does not work with keys.coinbase.com and vice versa. When they add this passkey, 1Pass asks if they'd like to update the existing item. If they choose "update" then they will have overwritten their keys.coinbase.com passkey and will have lost access to their crypto wallet secured by the keys.coinbase.com passkey.

So there are a few issues
1. We don't want a user adding a passkey for keys.coinbase.com to be offered the "update" option for coinbase.com
2. We don't want a user adding a passkey coinbase.com to be offered the "update" option for keys.coinbase.com
3. We don't want a user adding a passkey on keys.coinbase.com to "update" their existing keys.coinbase.com passkey.

Separately, I have updated my passkey for several sites to try to test the advice you gave me for viewing a previous passkey:

You can restore a previous passkey from an item's history: View and restore previous versions of items

You cannot view previous passkeys or restore them. I can see that I've updated the record, but I cannot restore an old passkey or see previous versions of it. I have tried this on iOS.