Skip to content

docs: correct cookie secure and SameSite defaults #173

Open

Description

@Bccorb

src/content/docs/reference/cookies-sessions-tokens.mdx:71-72 says secure is true only in production and sameSite is lax outside it. In the adapters, secure defaults to true always and SameSite derives from it (None when Secure).

  • Correct the page now.
  • Revisit after the v0.24 CSRF change, which moves the default to SameSite=Lax.

The review found no docs page that recommends something less safe than the SDK default.

Source

Internal security review of 2026-11-09 (doc claims table), read at 9cbc4fc. Found by reading code; nothing was executed. Status: Reported.

Activity

  1. added this to the v0.24 milestone on Nov 10, 2026
  2. added
    documentationImprovements or additions to documentation
    P1Next
    safeServes the safe promise: no lockout, no lock-in, honest
    v0.24Release v0.24: security release and stabilization
    on Nov 10, 2026
  3. Bccorb commented on Nov 10, 2026

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1NextdocumentationImprovements or additions to documentationsafeServes the safe promise: no lockout, no lock-in, honestv0.24Release v0.24: security release and stabilization

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions