Expand description
JwksFetcher — the validator’s HTTP seam (UT-1).
The OIDC validator never talks HTTP directly; it asks a JwksFetcher
for documents. This is what makes the AUTH-2 test matrix runnable with
no network: tests inject a fixture fetcher serving a canned
discovery document and JWKS. Production deployments either enable the
oidc-reqwest feature for the batteries-included
[ReqwestJwksFetcher] or adapt their own HTTP stack to the trait.
Structs§
- Fetch
Error - A fetch failure. Single-variant-with-message by design: the validator treats every fetch failure identically (degrade if a cache exists, reject otherwise) — distinguishing DNS from TLS from 503 buys nothing at this layer, and the message is preserved for the operator log.
- Fetched
Document - A fetched HTTP document plus the caching metadata the AUTH-8 policy needs.
Constants§
- MAX_
DOCUMENT_ BYTES - The most a discovery document or JWKS may weigh (IDENTITY-27). Real ones are a few KiB; anything past this is refused rather than read.
Traits§
- Jwks
Fetcher - Async document fetcher for OIDC discovery and JWKS documents.