- From: Matthew Miller via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Apr 2023 13:48:59 +0000
- To: public-webauthn@w3.org
> E.g., if I set the displayName as "A" with Browser X for the authenticator and I set the displayName as "B" with Browser Y for the same authenticator; I would get "A" and "B" for the credential generated by the same authenticator with different browsers. The flow that we imagined didn't involve the browser storing this string, rather it would flow through to the RP so that the RP had something it could nickname the credential. The client displaying this new value would strictly be for the user to optionally change the name that makes it back to the RP, and if the client handled the "enter a name" step of credential naming as part of the tail end of the registration ceremony then it would mean RP's wouldn't all have to implement similar functionality in their sites. And to be clear I don't think anyone suggested that the client or authenticator store whatever value the user ended up setting for the credential. The authenticator display name would be a default suggested name for the credential that the user could change one way, as it propagates through to the user. -- GitHub Notification of comment by MasterKale Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1880#issuecomment-1520196637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 April 2023 13:49:01 UTC