Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authenticator Attachment in Public Key Credential #1666

Closed
z11h opened this issue Aug 25, 2021 · 0 comments · Fixed by #1668
Closed

Authenticator Attachment in Public Key Credential #1666

z11h opened this issue Aug 25, 2021 · 0 comments · Fixed by #1668

Comments

@z11h
Copy link
Contributor

z11h commented Aug 25, 2021

In order for a site to know whether a local platform authenticator was used, or whether the user used another device and thus might want to register a local platform authenticator, this is a proposal that an authenticator attachment field be added to the public key credential response on both registration success & authentication success.

Thus, if the proposed authenticator attachment field of the attestation/assertion is “cross-platform”, and isUVPAA (i.e a user-verifying platform authenticator is available [1]) returns true, then sites should have the ability to offer to the user to register the current device's platform authenticator.

(In order to avoid superfluously re-registering devices if the user happened to use a phone or security key to sign in, even though the platform authenticator is already registered, the site may wish to track the registration status of the platform authenticator in local state. If the authenticator attachment was “internal” then the local state should be set to reflect that.)

Reference: #1637
[1] https://w3c.github.io/webauthn/#user-verifying-platform-authenticator

@z11h z11h changed the title Assertion Transports on Authentication Success Authenticator Attachment in Public Key Credential Sep 22, 2021
@w3c w3c deleted a comment from saara09 Oct 6, 2021
@equalsJeffH equalsJeffH added this to the L3-WD-01 milestone Oct 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants