How to distinguish FIDO2 devices
I want to distinguish the authentication device in webauthn.
I want to know if that is possible and how I can do it if possible.
Unfortunately there's no simple WebAuthn API function you can call to say, "give me the name of available authenticators". The WebAuthn API was intentionally designed to make it difficult to determine specific makes and models of authenticators in the name of greater user privacy.
The only reliable way to determine an authenticator's make and model is to request direct attestation during registration, and then cross-reference the aaguid you get back with a list you've collected and maintain yourself, or through something like the Fido Alliance Metadata Service.
Note: If you don't request
"direct"attestation you're likely to get back an obscuredaaguid:
For platform authenticators specifically you can try creating "heuristics", based on things like browser screen dimensions and User Agent analysis, that try to reliably determine whether system-level authenticators like Touch ID or Windows Hello are available. After a user successfully registers a credential with your site you'd want to store the results of your heuristics analysis with the credential to provide UX hints later during authentication (e.g. "we determined the user registered a Windows Hello credential, so show them 'Enter your Hello PIN to continue' UI during authentication.")
- Chrome DevTools Protocol WebAuthn.addCredential returns error
- E2E testing of WebAuthn authentication with Cypress - publickey-credentials-create' feature is not enabled
- How to intgrate Passkey in iOS App with custom Python backend using WebAuthn
- User verification failed when signing in to an iOS app with a passkey
- Does WebAuthn support finding out where passkeys are stored?
- Extract/export resident/private key created inside `navigator.credentials.create`?
- rpId validation failed in Passkeys PoC on Android using Jetpack Compose
- Why navigator.credentials.create return Credential instead of PublicKeyCredential in typescript?
- navigator.credentials is null on local server
- Is it possible to generate a WebAuthn attestation object?
- WebAuthn: Can't create public key. Promise is rejected
- Webauthn on localhost failed to pass navigator.credentials.get()
- Passkey assertion signature verification fail on iOS
- Challenge mismatch during authenticator attestion on iOS
- What options should I pass to node-cbor to decode WebAuthN passkey authenticatorData?
- Passkey Counter always 0 MacOS
- Webauthn: How can I know if a wrong fingerprint/PIN/Pattern auth attempt was made
- How to detect if the browser has support for webauthn
- What are the allowed RP IDs for the Public Key Credential create() and get()
- WebAuthn API not returning expected challenge token
- How to implement Passkeys
- How to remove WebAuthn credentials on Chrome MacOS?
- Webauthn - allowCredentials and credential selection
- How to manage Webauthn + user session?
- Webauthn - How to validate/verify returned registration auth data using React + Node.js
- Is Chrome ignoring WebAuthentication "userVerification" setting?
- Webauthn: ReferenceError: Can't find variable: PublicKeyCredential
- Using IP address as relying party ID in passkey
- WebAuthn exclude pin from options
- How to distinguish FIDO2 devices