- From: Ki-Eun Shin via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 May 2023 08:16:15 +0000
- To: public-webauthn@w3.org
Please correct me if I'm wrong. What I'm understanding is that browsers may offer the way for the user to configure the authenticator name. This configuration process by the user is not performed during the registration ceremony. If user sets certain name for the authenticator, the browser should have an ability to store such information so that such configuration keep surviving. If anything isn't configured, the browsers might return default name for the authenticator. If this is the case, as I've mentioned, such configured information is stored in the browser side and which causes the inconsistency between the names from the different browsers with same authenticator. As a RP, we would like to get meaningful consistent authenticator display name if the user creates credentials with the same authenticator regardless of browsers which the user runs. -- GitHub Notification of comment by Kieun Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1880#issuecomment-1534274488 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 May 2023 08:16:17 UTC