Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Solved
View Passkey History
I recently replaced a passkey for a domain and updated an existing Login entry for that domain with the new passkey. Unlike passwords, 1Pass does not keep an audit history of previously saved passkey...
It looks like you guys fixed this issue in a recent update (Aug 5th).
To anyone else that is interested, when you save a passkey with 1Pass now, it won't suggest to overwrite the existing entry.
https://releases.1password.com/android/stable/#1password-for-android-8.11.4
https://releases.1password.com/ios/stable/#1password-for-ios-8.11.4
"We’ve fixed an issue where 1Password would suggest to save a new passkey in existing login items, potentially causing some passkeys to be incorrectly overwritten."
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.
