- From: micolous via GitHub <noreply@w3.org>
- Date: Thu, 04 Jun 2026 06:18:53 +0000
- To: public-webauthn@w3.org
@timcappalli any feedback on my commentary above about bringing back `authenticatorDisplayName` (aka Option 3)? Providing a display name is a _much_ simpler solution for both RPs and credential managers that does not require any ongoing metadata updates, and meets the immediate requests of RPs (eg: https://github.com/webauthn-adoption/practical-webauthn/issues/6). This could be extended with something like a `authenticatorPresentationManifest` URL that allows an authenticator (or credential manager) author to provide multiple language translations (#2151) or icon options, and the author can update it on their own schedules. If an RP wants more control over the icons presented in their application's UI, they could use the URL itself to select from their own icon sets, which is roughly what they'd do anyway if combining the FIDO MDS and "community-driven lists". As I noted above, using AAGUIDs for display names is unreliable and difficult to manage, and this is impossible to fix without hardware recalls. Worse, the field could be confused with cryptographic attestation that a credential is _actually_ hardware-bound (per FIDO certification). -- GitHub Notification of comment by micolous Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2157#issuecomment-4619536349 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 June 2026 06:18:54 UTC