The JWT session plugin issues short-lived access tokens (JWTs) and long-lived refresh tokens. Access tokens are stateless (no DB lookup on every request). Refresh tokens are stored in the database and support rotation.Documentation Index
Fetch the complete documentation index at: https://docs.kavachos.com/llms.txt
Use this file to discover all available pages before exploring further.
Setup
Usage
Create a session
Verify an access token
Refresh
Revoke
Algorithms
| Algorithm | Config | Notes |
|---|---|---|
| HS256 | secret: string | Symmetric, simplest |
| RS256 | privateKey: CryptoKey, publicKey: CryptoKey | Asymmetric, for distributed verification |
Endpoints
| Method | Path | Description |
|---|---|---|
| POST | /auth/jwt/token | Create session |
| POST | /auth/jwt/refresh | Refresh tokens |
| POST | /auth/jwt/revoke | Revoke refresh token |
| GET | /auth/jwt/.well-known/jwks.json | JWKS endpoint (RS256 only) |
Access tokens are stateless. Revocation only affects refresh tokens. For immediate access token invalidation, use short TTLs (5-15 minutes).