Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
lodaka
2 years agoFrequent Contributor
Passkey implementation and usage
Hello, I wasn't sure where to post this; so, please move this thread to an appropriate place if needed.
After the recent update, I am now experimenting with the passkey function of 1Password. I've...
julia_v_1P
1Password Team
2 years agoHello Community Members,
Thank you for your insightful discussions regarding the passkey function in 1Password. Let's address the queries:
For lodaka:
When you enable passkey for a website, it's advisable to keep the original password/MFA entries until you're certain the Passkey works seamlessly across all devices and situations. Once confident, you can consider removing the old credentials.
Regarding the "Your device is not registered" message: Passkeys can be of two types: single-device credentials and multi-device credentials.
Single-device credentials, like a YubiKey, are specific to one device. They can only be validated on the device where they were initiated. This means if you set up a passkey of this type on one device, other devices won't recognize it.
On the other hand, many in the industry, such as Apple and 1Password, are moving towards multi-device credentials. These passkeys can be synced across different devices. So, even if you establish a passkey on one device, it can be recognized and utilized on another.
However, it's important to note that if you're using an Android phone, passkey functionality is not yet supported. Google is actively developing Android 14, which will introduce APIs allowing password managers like 1Password to create and utilize passkeys within Chrome and other supported apps. Once these APIs become available, 1Password is poised to offer support, enabling more seamless passkey use across Android 14 devices.
To rickapel:
- Yes, the implementation of passkeys might slightly differ depending on the website's infrastructure and security protocols.
- Ideally, a passkey should be device-independent. The message lodaka received could be from an additional security layer added by the website.
- Sharing passkeys within 1Password's family plan functions similarly to sharing any other data type. If you share a link or vault with another 1Password user, they should gain access.
- At this stage, you cannot import or export passkeys. We’re working closely with platform vendors and other password managers through the FIDO Alliance to create a secure way to import and export passkeys. We believe it’s your choice where to store and use your passkeys. Hopefully we’ll have more to share soon.
For GolferWHH:
Creating a step-by-step tutorial for setting up passkeys across various devices sounds invaluable. Ensuring users transition smoothly to new security measures is a priority. At the moment we have this support guide to help you get started with passkeys: Save and sign in with passkeys in your browser
For wlclev42:
Absolutely agreed. Transitioning from traditional passwords to passkeys is a significant shift, and understanding this new procedure is paramount. We're on it.
In essence, we're evolving alongside advancements in the security realm, ensuring 1Password remains a reliable guardian of your digital life. Your feedback propels us forward, and we thank you for your patience and insights.