Skip to content

Crypto: Token revocation via jti / signature storage (not hashing) #511

Description

@wim07101993

ADR requirement (§Hashing → Tokens): Generated tokens must not be stored; if revocation is needed, store the token id (jti) or the signature — no hashing required.

Current state (NOT FOUND): No revocation store / denylist; no jti persistence. Opaque tokens are stateless-encrypted and cannot be individually revoked.

Tasks:

  • Decide revocation model (store jti or signature for revocable token types).
  • Add a revocation store keyed by jti/signature with expiry-based cleanup.
  • Enforce revocation checks in the token verifier for applicable token types.

Acceptance: A revoked token id is rejected at verification; no full token or hashed token is stored.

Metadata

Metadata

Assignees

Labels

Fields

Priority

Low

Projects

Status
No status
Status
In review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions