- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Jul 2022 07:10:02 +0000
- To: public-webauthn@w3.org
Firstyear has just created a new issue for https://github.com/w3c/webauthn: == Facility for an RP to indicate a change of displayName to a discoverable credential == I was talking about this previously with @nsatragno, that there should be a method for an RP to indicate to a device that it may need to update it's knowledge of the users displayname. Let's consider I have a yubikey which contains a discoverable credentaila that I use in a "usernameless" flow (conditional ui). I update my displayname from William to Steve on the RP's user management interface. The next time I authenticate from my yubikey it would still prompt me to "login as William" (even though it will send the binary unique user id which correctly maps to my identity). Very few devices today publish administration tools allowing these to be updated which can be problematic for many types of person. A possible method to address this could be an extra "ceremony" type that indicates to the browser that the credential ID indicated SHOULD update it's knowledge of the display name. For ctap2.1 this would use https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html#updateUserInformation underneath. Other authenticators need to perform their own methods to update. This would allow the RP to list the authenticators registered by the user, along with an "update name" option that would initiate this possible workflow. There are plenty of possible other ideas that could resolve this, but I think at the least a way for an RP to indicate that a display name needs update would be really important and helpful! Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1779 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 July 2022 07:10:04 UTC