Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature-Request] Getting Authenticator device details #203

Closed
Chandra158 opened this issue Feb 12, 2024 · 2 comments
Closed

[Feature-Request] Getting Authenticator device details #203

Chandra158 opened this issue Feb 12, 2024 · 2 comments

Comments

@Chandra158
Copy link
Contributor

Chandra158 commented Feb 12, 2024

Description

During the Registration Verification phase, is it possible to get a suggestion for the created credential name (like: Chrome on Mac, FIDO2 security key)? (attached image from Google's Passkey settings page)
This is to display in the Passkeys Settings page after successful creation of a Passkey.

GoogleSettings-2

Possible Implementation

  1. Assuming we had already set attestation=direct in the RegistrationOptions
  2. With AAGUID value, search in the already saved json file
    • Source for the json file could be from the FIDO metadata server or from the community curated list of known aaguids (it also has a list which is a combination from FIDO and community curated)

Other information

  • I'm thinking if this should be implemented separately; but, it'd be nice to have this feature support within py_webauthn.
@Chandra158
Copy link
Contributor Author

@MasterKale I'd be happy to contribute if you're open to add this feature in this repo.

@MasterKale
Copy link
Collaborator

Hello @Chandra158 I apologize for leaving this hanging for so long. In the nearly a year since you submitted this issue there's been a lot of work done in the FIDO Alliance to try and make provider metadata (most if not all of the data available in the repo you linked) available in a "lite" version of FIDO MetadaService. I can't say much more about it at the moment, suffice to say if this is something that piques your curiosity then I suggest heading over to https://fidoalliance.org/metadata/ and signing up in the form at the bottom of the page to get updates when it finally launches.

As such metadata is relatively more dynamic than the various operations that need to be supported in a library like py_webauthn, I think it makes more sense to keep this kind of "suggested nickname" functionality out of this project. I'd say this is especially true given that the FIDO Alliance is this close to taking on the responsibility of offering up-to-date metadata for RPs that want to offer UX optimizations like what you show off above.

@MasterKale MasterKale closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants