Skip to content

Nonce and challenge store lifecycle #563

Description

@codebestia

Write apps/backend/docs/concepts-nonce-lifecycle.md for lib/nonce.ts: how challenge nonces are minted, stored, consumed and expired, for both the sign-in challenge and the separate device-link challenge.

Acceptance criteria:

  • Documents creation, single-use consumption and TTL for both nonce kinds
  • Explains why device-linking uses a separate nonce namespace from sign-in, so hammering one flow cannot lock out the other
  • Documents where nonces live and the behaviour across a restart or in a multi-node deployment
  • Explains the replay resistance this provides and its limits

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions