The FIDO Alliance recently launched its Convenience Metadata Service that's a collection of names and icons for any given AAGUID. The idea is that RP's can use this data to assign a nickname and display a credential manager icon for newly registered passkeys. This data is not for verifying attestation statements, only to enable better UX even with passkeys that return unattested AAGUIDs.
I'll likely create a new service in @simpelwebauthn/server to ingest this new MDS endpoint and expose its data to RPs by AAGUID. I could also see names+icons being returned in a successful call to verifyAuthenticationResponse() when this new hypothetical service is initialized.
The FIDO Alliance recently launched its Convenience Metadata Service that's a collection of names and icons for any given AAGUID. The idea is that RP's can use this data to assign a nickname and display a credential manager icon for newly registered passkeys. This data is not for verifying attestation statements, only to enable better UX even with passkeys that return unattested AAGUIDs.
I'll likely create a new service in @simpelwebauthn/server to ingest this new MDS endpoint and expose its data to RPs by AAGUID. I could also see names+icons being returned in a successful call to
verifyAuthenticationResponse()when this new hypothetical service is initialized.