Update JWT Auth
Configure JWT-bearer authentication for an endpoint. When enabled, every incoming request must present a valid JWT in the Authorization: Bearer <token> header — the platform fetches the IdP's public keys from the configured jwks_url, verifies the signature, and checks iss/aud claims against the configured values.
Successful verification optionally maps JWT claims into X-* headers passed to the agent (configured via claim_headers) — useful for stamping X-User-Id, X-Tenant-Id on every request without the upstream having to verify the token itself.
Layered with the main auth mode — JWT validation runs after the mode (basic/oauth/...) succeeds, so you can require both. Set enabled: false to disable without losing the configuration; the JWKS URL stays in the database for next time.
Path parameters
Request body
true to start enforcing JWT verification. When true, jwks_url is required.https://idp.example.com/.well-known/jwks.json). The platform refetches keys periodically and at signature-verification failure to handle key rotation.iss claim. Empty = don't enforce.aud claim. Empty = don't enforce.'{"sub": "X-User-Id", "email": "X-User-Email"}'). Stamped on the request before forwarding to the agent.Response (200 OK)
Empty body on success.
Errors
enabled: true without jwks_url.