robert1p - Appreciate the engagement 🙂
At this time, I don't have any details to share on the potential of exporting, but I'd be happy to pass your insight forward to the team as we work to make passkey use easier and more accessible.
If you don't mind, I have a couple follow up questions:
* In what way would being able to see the passkey details in plain text give you more confidence, when considering security, or otherwise?
* And in what way would this ability help improve your workflow (if any)?
I'm confused by the passkey demo (https://www.future.1password.com/passkeys/).
\n\nI enter a username, and it creates a Login Item in 1pw; no problem. I select Switch Account, enter a new username, and it creates a new Login Item in 1pw; no problem. I now attempt to login by selecting the first Login Item and it creates yet another Login Item (which appears to be a duplicate of the first Login Item); i.e. I now have 3 Login Items stored in 1pw. I assume this is a defect with the Demo.
It's also confusing that for each of the three Login Items, all the PassKeys appear to be identical; i.e. there are no details to indicate they differ in any way. While a simplistic interface is nice, I personally would like to see some way to view the underlying details of my PassKeys. For example, given the defect above, I can't tell if the duplicate Login Items have the same PassKey or different ones. (While \"Show\" PassKeys details would be preferable, \"Show\" PassKey Hash would be an improvement until then.)
1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided
\nBrowser:_ Not Provided
I'm confused by the passkey demo (https://www.future.1password.com/passkeys/).
\n\nI enter a username, and it creates a Login Item in 1pw; no problem. I select Switch Account, enter a new username, and it creates a new Login Item in 1pw; no problem. I now attempt to login by selecting the first Login Item and it creates yet another Login Item (which appears to be a duplicate of the first Login Item); i.e. I now have 3 Login Items stored in 1pw. I assume this is a defect with the Demo.
It's also confusing that for each of the three Login Items, all the PassKeys appear to be identical; i.e. there are no details to indicate they differ in any way. While a simplistic interface is nice, I personally would like to see some way to view the underlying details of my PassKeys. For example, given the defect above, I can't tell if the duplicate Login Items have the same PassKey or different ones. (While \"Show\" PassKeys details would be preferable, \"Show\" PassKey Hash would be an improvement until then.)
1Password Version: Not Provided
\nExtension Version: Not Provided
\nOS Version: Not Provided
\nBrowser:_ Not Provided
robert1p - Appreciate the engagement 🙂
\n\nAt this time, I don't have any details to share on the potential of exporting, but I'd be happy to pass your insight forward to the team as we work to make passkey use easier and more accessible.
\n\nIf you don't mind, I have a couple follow up questions:
\n* In what way would being able to see the passkey details in plain text give you more confidence, when considering security, or otherwise?
\n * And in what way would this ability help improve your workflow (if any)?
At this time, I don't have any details to share on the potential of exporting, but I'd be happy to pass your insight forward to the team as we work to make passkey use easier and more accessible.
\n\nIf you don't mind, I have a couple follow up questions:
\n* In what way would being able to see the passkey details in plain text give you more confidence, when considering security, or otherwise?
\n * And in what way would this ability help improve your workflow (if any)?
