Expand description
JTI-based token revocation.
Revoked token identifiers are stored in a backend that supports TTL-based expiry. Retention must include the verifier’s clock leeway, including its final accepted second.
Structs§
- InMemory
Revocation Store - In-memory revocation store with lazy expiry sweeps. Suitable for single-instance deployments and testing.
- Revocation
Health - Local, nonblocking health of a revocation dependency.
- Revocation
Identity - Signature-verified identity needed to check an ancestor’s revocation.
Enums§
- Revoke
Outcome - Whether a revoke request created a new entry.
- Revoked
By - The rule which revoked a validated token.
Traits§
- Revocation
Store - Trait for pluggable revocation backends. The harness wires this to
the
StateStore(Redis for distributed deployments, in-memory otherwise).