Repository navigation
Conversation
…is unreachable Managed Kubernetes offerings may publish an OIDC discovery document whose jwks_uri points at an API-server load balancer VIP that is unreachable from the pod network (observed on ACK, where the SLB whitelist covers node subnets but not pod CIDRs). Every JWT verification then fails with signing keys unavailable. The JWKS endpoint is served by the same API server that just served the discovery document, so when fetching the advertised jwks_uri fails and its origin differs from the issuer's, retry once with the same path on the issuer's origin. Issuers whose jwks_uri is same-origin (the common case) see no behavior change. Signed-off-by: zhousiyu <zhousiyu@kanzhun.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…is unreachable
Managed Kubernetes offerings may publish an OIDC discovery document whose jwks_uri points at an API-server load balancer VIP that is unreachable from the pod network (observed on ACK, where the SLB whitelist covers node subnets but not pod CIDRs). Every JWT verification then fails with signing keys unavailable.
The JWKS endpoint is served by the same API server that just served the discovery document, so when fetching the advertised jwks_uri fails and its origin differs from the issuer's, retry once with the same path on the issuer's origin. Issuers whose jwks_uri is same-origin (the common case) see no behavior change.
Why is this needed? (Or link the issue. Open one first for features, API, install or CI changes.)
Fixes #
AI use: