-
Notifications
You must be signed in to change notification settings - Fork 61
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
UserEntity.DisplayName should not have omitempty #183
Labels
Comments
jameshartig
added
status/needs-triage
Issues that need to be triaged.
type/potential-bug
Potential Bugs
labels
Nov 28, 2023
james-d-elliott
added
type/bug
Something isn't working
and removed
type/potential-bug
Potential Bugs
labels
Nov 28, 2023
Thanks for reporting I'll fix and release this today. For reference the docs you linked to are a draft but this is valid regardless. |
james-d-elliott
added a commit
that referenced
this issue
Nov 28, 2023
This fixes an issue where the displayName value for a user entity was omitted in error. See https://www.w3.org/TR/webauthn-3/#dom-publickeycredentialcreationoptions-user and https://www.w3.org/TR/webauthn-3/#dictdef-publickeycredentialuserentity (and the same links for level 2). Fixes #183
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Version
0.9.1
Description
but when a user is registering for the first time the RP might not require the user to enter their name and the displayName might be empty, which would then get omitted and cause an error in JavaScript when calling
navigator.credentials.create
.Reproduction
wa.BeginRegistration
.navigator.credentials.create
Expectations
Expectation is that the resulting JSON would contain
displayName: ''
but insteaddisplayName
is undefined.Documentation
https://w3c.github.io/webauthn/#dom-publickeycredentialcreationoptions-user
The text was updated successfully, but these errors were encountered: