Skip to content

OIDC token authenticator should expire cached JWKs based on server-provided cache headers #142100

Description

@everettraven

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.

Activity

  1. added
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Sep 14, 2026
  2. kubernetes-prow commented on Sep 14, 2026

    @kubernetes-prow
    Contributor

    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/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.

  3. yashaggarwal85d commented on Oct 26, 2026

    @yashaggarwal85d

    /sig auth

  4. added
    sig/authCategorizes an issue or PR as relevant to SIG Auth.
    and removed
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Oct 26, 2026
  5. yashaggarwal85d commented on Oct 26, 2026

    @yashaggarwal85d

    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.

  6. moved this to Needs Triage in SIG Authon Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/authCategorizes an issue or PR as relevant to SIG Auth.

    Type

    No type

    Projects

    • Status
      Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions