Repository navigation
feat(oidc): allow internal service transport - #195
Merged
Merged
Conversation
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
1 participant
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.
Cluster services could keep a public OIDC issuer identity only by sending discovery and confidential token grants through public ingress. That prevented an exact in-cluster NetworkPolicy lane for services such as Rudaia Billing.
This adds explicit deployment-owned discovery and token transport endpoints to
OidcClientBuilderandfrom_env. The discovery document must still declare the configured public issuer, unsafe HTTP endpoints remain rejected, and plain HTTP is limited to loopback or Kubernetes Service DNS names.Validation:
cargo fmt --all -- --checkcargo test -p cli-framework-oidc --features client(84 tests passed)cargo clippy -p cli-framework-oidc --features client --all-targets -- -D warnings