Skip to main content

Passkeys - FIDO2 Passwordless Authentication

About 2 min read

A passkey is a passwordless authentication method based on the FIDO2 (Fast IDentity Online 2) standard that authenticates users with public-key cryptography instead of passwords. Rather than entering a password, users can log in to a service using the same method they use to unlock their device, such as fingerprint recognition, facial recognition, or a PIN. It is designed to resist phishing, and no shared secret such as a password is kept on the server.

Historical Background

The FIDO specifications on which passkeys are built were developed by the FIDO Alliance, established in 2012. In March 2019, the W3C recommended WebAuthn as a web standard, making passwordless authentication technically possible in browsers. In May 2022, Apple, Google, and Microsoft jointly announced plans to expand their support for this standard. According to the FIDO Alliance, passkeys are either synced across a user's devices or bound to a single device.

How It Works

Passkeys are based on public-key cryptography. When you register with a service, a pair consisting of a private key and a public key is generated on your device. The private key is stored in a secure area of the device (a secure enclave or TPM), and only the public key is sent to the service. At login, the device signs a challenge sent by the service with the private key, and the service verifies it with the public key. As a result, even if the server-side data is breached, there are no passwords to steal.

Why Passkeys Resist Phishing

One weakness of passwords is that they can be stolen simply by getting someone to type them into a convincing fake site. Passkeys break this structure itself. First, there is no secret for the user to type in the first place, so the trick of "make them enter it and steal it" cannot work. Furthermore, a passkey is created bound to the site where it was registered, and the browser or OS checks the destination, so on a fake site with a different domain the signing procedure never even starts. Rejecting fake sites by mechanism rather than relying on human vigilance is why passkeys are described as phishing-resistant. For users, the simplicity of having nothing to memorize and unlocking with biometrics or similar goes hand in hand with that safety.

Authentication Flow

Service sends a challenge
Verify identity with biometrics / PIN
Sign with the private key
Verify with the public key
Login complete

Current State in Practice and Measures for the Transition Period

The major platforms from Apple, Google, and Microsoft support passkeys. However, not all services support passkeys, so for the time being they will continue to be used alongside passwords. As a practical consideration, for passkeys bound to a single device, recovery methods need to be secured in advance in case the device is lost or fails. If you enable cloud synchronization through iCloud Keychain or Google Password Manager, you can migrate smoothly even when replacing a device. For services that do not yet support passkeys, the combination of a sufficiently long random password and two-factor authentication remains an available option.

Was this article helpful?

Related Terms