Resolve the JWKS Cache-Control max-age (seconds) for a deployment.
Consumed only by the JWKS route (discovery does not advertise cache
metadata), so this is not a shared anti-drift helper like
resolveJwksPath — it simply centralizes the config key + default.
Intentionally lenient: the config schema is the authoritative guard (it
rejects negative / non-integer / non-number values at parse time), so at
runtime configured is either a valid non-negative integer or absent.
The defensive check falls back to the default for callers that bypass the
schema (hand-built config objects).
Resolve the JWKS
Cache-Controlmax-age (seconds) for a deployment. Consumed only by the JWKS route (discovery does not advertise cache metadata), so this is not a shared anti-drift helper likeresolveJwksPath— it simply centralizes the config key + default.Intentionally lenient: the config schema is the authoritative guard (it rejects negative / non-integer / non-number values at parse time), so at runtime
configuredis either a valid non-negative integer or absent. The defensive check falls back to the default for callers that bypass the schema (hand-built config objects).