Add passkeys without weakening account recovery

Add passkeys without weakening account recovery is easiest to get right when the boundary is named before the implementation begins. Decide which system owns the decision, which inputs are trusted, what the caller can observe, and what must remain private. That framing prevents a local optimization from quietly becoming an undocumented protocol.

Passkeys can resist phishing because the authenticator signs a challenge for a specific relying party and origin. The security benefit disappears if the server skips origin or challenge validation, treats a display name as an identity, or offers a recovery path weaker than the credential it replaces. Implement registration, authentication, and recovery as one lifecycle.

Store the credential ID, public key, sign counter, transports, creation time, last use, and user association. Generate a fresh challenge server-side, bind it to the intended operation and session, and expire it quickly. The relying party ID and allowed origins must be configuration, not client input. Keep account recovery and credential management behind an authenticated step-up.

Write the model down as a small state diagram or table before selecting a library. Identify the durable state, the derived state, and the transitions that may be retried. This makes it easier to compare a managed service with an in-process implementation and to explain why a particular trade-off is acceptable for this workload.

The critical failures are accepting a challenge from another session, skipping origin or RP ID checks, failing to handle cloned authenticators, exposing credential identifiers in logs, and allowing an email-only reset to bypass passkey protection. Multi-device credentials also change the meaning of a sign counter; follow the authenticator guidance instead of treating every counter anomaly as proof of compromise.

A resilient design assumes that inputs are incomplete, dependencies are slow, operators make mistakes, and requirements will change. Put limits at the boundary, return errors that a caller can act on, and preserve enough context to distinguish a bad request from an unavailable dependency. Avoid broad fallbacks that make an unsafe state look successful.

Use a well-reviewed WebAuthn library and pass its expected origin, RP ID, challenge, and user verification policy explicitly. During registration, require a verified account context and store only the public credential data. During login, map the credential ID to the account, verify the assertion, update the counter carefully, and issue a session with the same authorization checks as other login methods.

Keep the first implementation narrow enough to review line by line. Make inputs, outputs, authorization context, and failure behavior explicit instead of hiding them behind a convenience helper. The example should be safe to run with synthetic data, emit a correlation identifier, and leave a durable artifact that another engineer can inspect after the request has finished.

Test registration and login on two browser families, a platform authenticator, a roaming key, canceled prompts, wrong origins, expired challenges, reused challenges, unknown credentials, and a disabled account. Verify recovery requires an equivalent or stronger proof and that removing the last credential prompts the user to establish a safe alternative.

Use a small test matrix that covers the ordinary path, an empty or missing input, a duplicate request, a timeout, a permission failure, and a version mismatch. Assert both the response and the side effects. When a test fails, compare the observed transition with the model rather than adding a retry or widening a timeout without evidence.

Monitor registration success, assertion failures by reason, challenge expiry, counter anomalies, recovery use, and credential age. Give users a clear credential list and a way to revoke one device. Keep a staffed recovery process for high-value accounts and record its evidence. If a relying-party origin changes, treat it as a planned migration, not a silent configuration edit.

Give the operator a bounded recovery action: replay a safe event, rebuild a derived view, rotate a credential, drain a queue, or roll back a compatible revision. Record the owner, retention period, alert threshold, and rollback condition next to the implementation. A runbook is useful only when it can be followed without reconstructing the design from production logs.

For a small service, prefer the design with the fewest hidden states that still meets the application security requirement. Add a managed dependency when it removes a failure mode you can measure, not simply because it is popular. Keep the interface replaceable by isolating provider-specific code behind a narrow adapter and by testing the behavior your users depend on.

Revisit the decision when traffic shape, data sensitivity, team ownership, or recovery objectives change. A design that is excellent for a single tenant or a low-volume internal tool can be the wrong design for a public multi-tenant path. Record the assumptions so the next change starts with evidence rather than folklore.

Before publishing a change related to add passkeys without weakening account recovery, write down the input contract, authorization context, state transitions, limits, and user-visible errors. Identify the smallest synthetic dataset that demonstrates the normal path and the smallest dataset that demonstrates the dangerous path. Add a correlation ID to the example, make retries deliberate, and decide which artifacts can be retained for support without copying secrets or unnecessary personal data. This checklist is deliberately boring: repeatable release evidence is more valuable than a clever demo.

Use a disposable environment to exercise the implementation with realistic concurrency and a dependency failure. Compare the observed result with the contract, then record the measured latency, resource use, and recovery action. If a managed service or library is involved, pin its version and capture the relevant configuration. Ship behind a reversible change when the behavior is new, and schedule a follow-up review after real traffic reveals assumptions that a test fixture could not.

Use the W3C WebAuthn specification, FIDO Alliance deployment guidance, and the browser implementation documentation. Review the OWASP Authentication Cheat Sheet for recovery and session handling, not only the cryptographic ceremony.

Prefer primary protocol specifications, vendor security documentation, and measured behavior from a disposable environment. Read the failure and deprecation sections, not only the happy-path quick start. A short reference list attached to the code gives future maintainers a way to distinguish an intentional constraint from an accidental implementation detail.