- From: Matthew Miller via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Feb 2023 03:07:53 +0000
- To: public-webauthn@w3.org
> If what is currently displayed is displayname then having the name be "mmiler@beta_environment" would be what was originally intended. [`displayName`](https://www.w3.org/TR/webauthn-2/#dom-publickeycredentialuserentity-displayname) doesn't read like the kind of value that'd look like "mmiller@beta_environment". The name examples in the spec constrains thoughts of what are appropriate values for this field to "full name" representations of the user. Perhaps there's a chance here to expand the examples to denote this could be used for my "Beta Environment" example. > A [human-palatable](https://www.w3.org/TR/webauthn-2/#human-palatability) name for the user account, intended only for display. For example, "Alex Müller" or "田中倫". The [Relying Party](https://www.w3.org/TR/webauthn-2/#relying-party) SHOULD let the user choose this, and SHOULD NOT restrict the choice more than necessary. [PublicKeyCredentialUserEntity](https://www.w3.org/TR/webauthn-2/#dictdef-publickeycredentialuserentity)'s [`name`](https://www.w3.org/TR/webauthn-2/#dom-publickeycredentialentity-name) property seems similar, too - this field seems like it'd be where the user's email address might go: > The name field is the name of the account to display to the user in whatever format the RP wants. So if we wanted to encourage full use of `PublicKeyCredentialUserEntity`, perhaps we can clarify these two further with example use cases to satisfy my proposal. -- GitHub Notification of comment by MasterKale Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1852#issuecomment-1429045498 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 February 2023 03:07:54 UTC