WebAuthn Passkey

Outcome: Design or review WebAuthn Passkey for this system while keeping data correct, secure, and easy to operate. User context: A customer adds a passkey after signing in again. The server stores the credential ID and public key. It sends a new challenge tied to `howtovibeui.com`. It checks the origin, RP ID, challenge, signature, and user verification. A lost device is handled with another passkey or a reviewed recovery flow, not a security question. Technical concept or control: WebAuthn Passkey. Why it fits: Offer passkeys for normal or extra-secure sign-in. Include safe setup, a way to manage several credentials, and account recovery. Do not use it when: Do not claim every passkey stays on one device or skip server challenge checks. Never remove the last recovery path without clear confirmation. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.