...
Supplementary Passkey Provider Metadata
Without an additional source of metadata, authenticators/providers that are not part of the FIDO Metadata Service will remain ‘unknown’ to the registration/admin user interfaces. Typically, these are software authenticators that cannot provide "trusted" attestations (they self-attest) that can be verified by a trust anchor in the FIDO metadata service.
However, if you want the end-user to see a name and icon for ‘software’ authenticators they register in the registration inteferface e.g. ‘Bitwarden’, or ‘Windows Hello’, you will need to enable the supplementary passkey provider metadata support. To do this you must first download a suitable AAGUID JSON file based on the JSON schema attached. Next, enable support in the plugin by setting the property idp.authn.webauthn.metadata.aaguid.enabled to true and point to the AAGUID JSON file using the property idp.authn.webauthn.metadata.aaguid.passkeyAaguidFile.
This is taken from the passkey-authenticator-aaguid GitHub repository.
Reference
...