WebAuthn Compatibility

User Presence - The browser supports a physical user interaction to establish an event is not being initiated by a remote attacker. Support for user presence is mandatory for environments supporting WebAuthn, and for devices to be certified by the FIDO alliance. Support for Resident Key / Discoverable Credentials, User Verification or Passkeys means User Presence over FIDO2 is possible.

Resident Key / Discoverable Credential - The browser supports WebAuthn credentials stored on the authenticator. These credentials can be read to identify the user account without the user manually providing them.

User Verification (PIN / Biometric) - The browser supports an interface to allow a user to verify their identity via entering a WebAuthn PIN or Biometric.

Passkeys - The browser supports securely creating and using passkeys on a roaming authenticator.

CTAP 1 / U2F Legacy Support - The browser has legacy support for authenticators only supporting User Presence over U2F.

*Notes on Chrome differences from other browsers

NFC support has been excluded since NFC is not supported on macOS browsers.

*Safari & Firefox will not allow users to set a PIN for User Verification if one is not already set.

**Bug for FIDO/U2F registration issues for WebKit/Safari: https://bugs.webkit.org/show_bug.cgi?id=247344

Verified with iPhone XR

Most browsers on Apple mobile devices use Apple WebKit. As such, these browsers will have all the same functionality available.

*Browsers on iOS are not able to set a PIN for user verification (UV) if one is not already set. Requests to create a credential that requires UV may appear to succeed, but create a credential that will not require a PIN.

Verified with iPad 6th generation (Lightning), iPad Air (USB-C) 4th generation, and iPad Pro 2018 (USB-C)

Most browsers on Apple mobile devices use Apple WebKit. As such, these browsers will have all the same functionality available.

NFC tests have been excluded since NFC is not supported on iPadOS browsers. USB-C is only available on iPad Pro and 4th and 5th generation iPad Air models.

*Browsers on iPadOS are not able to set a PIN for user verification (UV) if one is not already set. Requests to create a credential that requires UV may appear to succeed, but create a credential that will not require a PIN.

Verified with Pixel 6 & Google Play Services 24.16

Android support for FIDO2 is linked to Google Play Services, and may be available on Google Play Protect certified devices running Android 9 or later, as long as they are running a current version of Google Play Services, and have a screen lock configured.

Currently the Android platform only supports the CTAP 1 (U2F) protocol over NFC. Support for Resident Keys / Discoverable Credentials, User Verification, and passkeys is available over USB.

*Android will prevent the use of passkeys / resident keys / discoverable credentials on a security key, if there is already at least one synced passkey in Google password manager for the same web site.

**Bug for Firefox mobile support of security keys: https://bugzilla.mozilla.org/show_bug.cgi?id=1888654