Passkeys can be used for user authentication when the system meets specific requirements, such as compatible operating systems, necessary hardware like TPM or Secure Enclave, and support from the passkey provider. Typically, passkeys work on modern devices that run updated operating systems and have secure hardware components. Additionally, a WebAuthn server support is required at the relying party.
To use passkeys, devices must meet certain system and hardware requirements. These include:
To use passkeys, support from a passkey provider, such as Apple’s iCloud Keychain or Google Password Manager is necessary. These providers store the passkeys in the cloud, allowing users to authenticate across multiple devices. Users must have a registered cloud account with these providers to utilize passkeys. Alternatively, a third-party passkey provider (password manager) like 1Password or Dashlane can also be used.
For passkeys to function, the relying party (such as a website or app) must implement a WebAuthn server. This server is responsible for handling the creation, storage, and validation of passkeys during the authentication process. Without a WebAuthn-compliant server, passkeys cannot be used.
Corbado is the Passkey Intelligence Platform for CIAM teams running consumer authentication at scale. We help you see what IDP logs and generic analytics tools can't: which devices, OS versions, browsers and credential managers support passkeys, why enrollments don't turn into logins, where the WebAuthn flow fails and when an OS / browser update silently breaks login, all without replacing Okta, Auth0, Ping, Cognito or your in-house IDP. Two products: Corbado Observe layers observability for passkeys and any other login method. Corbado Connect adds managed passkeys with analytics built in (alongside your IDP). VicRoads runs passkeys for 5M+ users with Corbado (+80% passkey activation). Talk to a Passkey Expert →
Table of Contents
Related Articles