-
Notifications
You must be signed in to change notification settings - Fork 172
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
What extension data is in AuthenticatorAssertionResponse.authenticatorData? #418
Comments
Yep - that's a bug. It should be "authenticator extension outputs". I'll file a quick PR to fix this and ask @equalsJeffH to review it and merge it. Thanks for the catch! |
selfissued
added a commit
to selfissued/webauthn
that referenced
this issue
Apr 22, 2017
…esponse.authenticatorData?
WebAuthnBot
pushed a commit
that referenced
this issue
Apr 23, 2017
…n AuthenticatorAssertionResponse.authenticatorData? (#421)
fixed by PR #421 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's documented as
and that section says the extension data is "a CBOR [RFC7049] map with extension identifiers as keys, and authenticator extension inputs as values". It's odd to see inputs stored in a returned structure. Should that be "client extension outputs" instead?
If it's "authenticator extension outputs", then I'm curious where the client outputs wind up.
The text was updated successfully, but these errors were encountered: