Page MenuHomePhabricator

Automatically generate passkey name based on AAGUID
Closed, ResolvedPublic

Description

The passkey creation UI in T410336 does not contain an input for the passkey name, and instead we'll need to automatically generate a name. We should do this based on the AAGUID, which identifies the password manager that created the passkey (and possibly based on other things like which browser was used -- I've asked @EMill-WMF and @KieranMcCann-WMF to decide what these auto-generated names should look like).

  • Figure out how to set up an AAGUID -> user readable name mapping
  • Integrate that into the passkey creation process once T410336 is done

Event Timeline

Given the scope, I think it seems reasonable to start with a simple lookup table that maps known AAGUIDs to readable device names (e.g. Google Password Manager, iCloud Keychain, YubiKey 5 Series, etc...). This can be either hardcoded at first, or stored in a small static file. I think that is a good starting point rather than some more complex approach for now.

For unknown AAGUIDs, a possible fallback is to assign a generic label, either something derived from the AAGUID itself (such as a short prefix) or a neutral name like “Passkey on this device.”

We should clarify what UX we prefer for this case.

Catrope raised the priority of this task from Medium to High.Dec 13 2025, 1:02 AM

Change #1220389 had a related patch set uploaded (by Mmartorana; author: Mmartorana):

[mediawiki/extensions/WebAuthn@master] Refactor WebAuthn registration to use API endpoint

https://gerrit.wikimedia.org/r/1220389

Change #1220389 merged by jenkins-bot:

[mediawiki/extensions/WebAuthn@master] Refactor WebAuthn registration to use API endpoint

https://gerrit.wikimedia.org/r/1220389