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

add invocation of authenticatorCancel to step 8 of makeCredential ? #124

Closed
equalsJeffH opened this issue Jun 9, 2016 · 0 comments
Closed

Comments

@equalsJeffH
Copy link
Contributor

extracted from: https://lists.w3.org/Archives/Public/public-webauthn/2016Jun/0070.html

Assuming that a system has recognized three available authenticators, when a makeCredential() request is called all three authenticators will display a message asking a user to approve making a credential. [...] what happens when the first authenticator succeeds? If a user selects ok / yes / approve, do the other two authenticators still display their confirmation messages and allow additional registration responses? Or should the client send authenticationCancel() to the two other authenticators after the first successful result?

To a fair degree this is all up to "the platform" (OS+UA+authnrs), I
think, although invoking authenticatorCancel on any remaining
issuedRequests entries /could/ be added to the last bullet item of step 9
in..

https://w3c.github.io/webauthn/#makeCredential

..as you suggest, but others should probably weigh-in.

@equalsJeffH equalsJeffH added this to the CR milestone Jun 9, 2016
vijaybh added a commit that referenced this issue Jul 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants