Skip to content
Get startedGetting started →

Authenticator support

mera requires three things from the authenticator stack: the WebAuthn PRF extension, discoverable credentials, and user verification. Passkeys and the PRF extension defines all three.

In the table, means a live PRF create + get cycle has been confirmed end-to-end; Not supported means a live test did not return PRF.

AuthenticatorBrowserOSStatusSupported since
1Passwordany browser with 1Password activeany2.26.1 beta / Android 8.10.38 beta (2024-07)
iCloud KeychainSafariiOS 18+Safari 18 / iOS 18 (2024-09)
iCloud KeychainSafarimacOS 15+Safari 18 / macOS 15 (2024-09)
iCloud KeychainChromemacOS 15+Chrome 132+ (2025-01)
iCloud KeychainChromeiOS 18+Safari 18 / iOS 18 (2024-09)
iCloud KeychainFirefoxmacOS 15+Firefox 139+ (2025-05)
Google Password ManagerChromeAndroidKnown by 2026-06
Google Password ManagerChromeDesktop (signed-in)Chrome 132+ (2025-01)
Chrome profileChromeDesktopNot supported (2026-06-01)
Google Password ManagerEdgeAndroidKnown by 2026-06
Windows Password ManagerEdgeWindows 11 25H2+Windows 11 25H2 + 2026-02 update
Windows Password ManagerChromeWindows 11 25H2+Chrome 147+ (2026-04)
Windows Password ManagerFirefox 148+Windows 11 25H2+Firefox 148+ (2026-02)
YubiKey 5C NanoChromeDesktopChrome 116+; YubiKey 5.2+ hmac-secret
BitwardenChromeDesktopNot supported (2026-06-01)
DashlaneChromeDesktopNot supported (2026-06-01)
Proton PassChromeDesktopLatest public version (2026-06)

On desktop Chrome, only passkeys saved to Google Password Manager carry PRF. The local profile authenticator lacks hmac-secret, the CTAP primitive behind PRF.

Chrome may create the passkey in the local profile instead of Google Password Manager when its “Offer to save passwords and passkeys” setting is off, or when a third-party password-manager extension intercepts WebAuthn and relays the browser fallback ceremony. Either way the passkey exists but returns no PRF output, so mera cannot use it and createPasskeyWithPrfOutput fails.