You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OIDC token authenticator should expire cached JWKs based on server-provided cache headers #142100
During the review process of #142012 we found that JWKs don't have an expiration associated with them, meaning that there is no mechanism for a JWK publisher to indicate a maximum time in which that JWK data should remain valid before needing a cache refresh.
This issue is spun out of #142012 for this to be tracked as a follow-up.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Details
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Hi @everettraven, are you planning to pick this up? If not I'd like to take it. I have a small change ready that wraps the RemoteKeySet in the oidc authenticator, reads max-age / Expires off the JWKS response and drops the cached keys once they're stale (with a 1 minute floor so it stays under the JWKS rate limit). Happy to go another way if you'd rather fix it in go-oidc, or put it behind a feature gate.
Activity
kubernetes-prow commentedon Sep 14, 2026
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.The
triage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.Details
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
yashaggarwal85d commentedon Oct 26, 2026
/sig auth
yashaggarwal85d commentedon Oct 26, 2026
Hi @everettraven, are you planning to pick this up? If not I'd like to take it. I have a small change ready that wraps the RemoteKeySet in the oidc authenticator, reads max-age / Expires off the JWKS response and drops the cached keys once they're stale (with a 1 minute floor so it stays under the JWKS rate limit). Happy to go another way if you'd rather fix it in go-oidc, or put it behind a feature gate.