All posts
Security

Rolling Out Passkeys in 2026: A Practical Guide, Including the Decision You Cannot Undo

By

October 26, 2026

7 min read

Passkeys are now supported by every major platform and can move between password managers. How to roll them out without locking anyone out: enrolment prompts, recovery, the relying-party ID you must choose correctly the first time, and what Cognito, Auth0 and the rest do for you.

Passkeys
WebAuthn
Amazon Cognito
Authentication
FIDO

Where passkeys stand

Passkeys are phishing-resistant by design: the credential is bound to your domain, so a look-alike site cannot use it. They sync across a user's devices through their platform or password manager, and since Apple's 2026 operating systems they can be moved between participating credential managers using the FIDO Alliance's Credential Exchange formats: removing the old worry that a passkey locks someone into one ecosystem. Every major identity provider supports them; Cognito added passkeys to its Essentials and Plus tiers in November 2024.

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

The decision you cannot undo: the relying-party ID

A passkey is created for a relying-party ID — a domain — and browsers only offer it on that domain and its subdomains. Choose app.example.com and the passkey will never appear on example.com or on a new auth.example.com; choose example.com and it works on all of them. Changing it later does not migrate anything: every passkey already enrolled silently stops being offered. Use the registrable parent domain unless you have a specific reason not to. On Cognito, with managed login and a custom domain, the RP ID defaults to the custom domain's full name — check it before the first user enrols.

A rollout that does not lock people out

  1. Offer, do not force: prompt existing users to add a passkey right after a successful sign-in, when they have just proved who they are.

  2. Keep a second factor of recovery — email or a backup method — until most users have passkeys on more than one device.

  3. Show which passkeys an account has and let users name and remove them; a lost phone should be a settings change, not a support ticket.

  4. Use conditional mediation (passkey autofill) on the sign-in form, so returning users are offered their passkey without hunting for a button.

  5. Measure: enrolment rate, sign-in success rate with passkeys versus passwords, and recovery requests.

What your provider does for you

Managed login pages — Cognito's, Auth0's, Clerk's and others' — handle the WebAuthn ceremonies and the prompts. If you build your own sign-in, Cognito exposes the steps as API calls (StartWebAuthnRegistration, then completing with the browser's response), authorised with the user's access token. Either way, the RP ID decision and the recovery policy are yours.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 26, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.