4 ms·
Disclosure, I work for FusionAuth. This is the primary issue with passkeys. When FusionAuth implemented WebAuthn/passkeys last year[0], we decided to have pass
by mooreds 4y ago
Disclosure, I work for FusionAuth.
This is the primary issue with passkeys. When FusionAuth implemented WebAuthn/passkeys last year[0], we decided to have passkeys be a separate, additional login method, just like social sign-on or magic links, for this exact reason.
My understanding is that there is some work in the next version of WebAuthn[1] to allow sharing of passkeys across devices, addressing this user experience issue.
0: https://fusionauth.io/docs/v1/tech/premium-features/webauthn/ https://fusionauth.io/docs/v1/tech/premium-features/webauthn...
1: https://www.w3.org/TR/webauthn-3/ https://www.w3.org/TR/webauthn-3/
- tehbeard 4y agoDoes there need to be work on webauthn for it? (maybe some wording sugggestions around "resident keys" which I think are meant to be persistent and within a singleTPM or such, but no technical constraints beyond that afaik). My understanding was passkeys was just Apple Marketing(tm) around their implementation and integrating it with iCloud/keychain?
- mooreds 4y agoLooks like they have had a section on key loss since at least webauthn 2[0], and explicitly rule out backing up keys. The suggested answer is "use multiple devices" which doesn't work great with platform authenticators (which are tied to a device). From the spec: > This specification defines no protocol for backing up credential private keys, or for sharing them between authenticators. In general, it is expected that a credential private key never leaves the authenticator that created it. Losing an authenticator therefore, in general, means losing all credentials bound to the lost authenticator, which could lock the user out of an account if the user has only one credential registered with the Relying Party. Instead of backing up or sharing private keys, the Web Authentication API allows registering multiple credentials for the same user. For example, a user might register platform credentials on frequently used client devices, and one or more roaming credentials for use as backup and with new or rarely used client devices. So I guess you are right, it is on the vendors to handle backing up the keys from devices. 0: https://www.w3.org/TR/webauthn-2/#sctn-credential-loss-key-mobility https://www.w3.org/TR/webauthn-2/#sctn-credential-loss-key-m...