Security1 min read
Passkeys for SaaS: what actually changes in your auth stack
Passkeys remove the password, but not the account-recovery problem, the session layer, or your need for good audit logs. A practical tour of what to build and what to keep.
Passkeys are public-key credentials (WebAuthn) that are synced across a user’s devices by their platform. The server stores a public key. The private key never leaves the user’s authenticator. There’s no shared secret to phish, reuse or leak in a breach.
What changes
- Registration becomes a challenge–response ceremony: your server issues a random challenge, the browser asks the authenticator to create a key pair bound to your domain, and you store the public key and credential ID.
- Sign-in is another challenge, signed by the private key and verified with the stored public key.
- Phishing resistance comes from origin binding: a credential for
app.example.comsimply won’t sign for a look-alike domain.
What doesn’t change
- Sessions. After authentication you still issue a session (an HttpOnly, Secure, SameSite cookie) and still need rotation, expiry and revocation.
- Account recovery. Users lose devices. Your recovery path is now your weakest link, so treat it with the same rigor as login.
- Authorization. Passkeys tell you who someone is, not what they may do.
A sensible rollout
Offer passkeys as an additional sign-in method first, prompt users to add one after a successful login, and only then consider making them the default. Measure how many users have at least one passkey before you let anyone remove their password.
- #auth
- #webauthn
- #passkeys