Support for OIDC provider that does not allow CORS on the metadata endpoint #270
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.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
If an OIDC provider does not allow CORS on the metadata endpoint, it should be possible to manually configure the
oidc-client
with these additional settings.oidc-client docs
This PR allows to configure these settings in the helm chart. It also proxies the jwks endpoint of the oidc provider if
oidc.metadata.jwks_uri === '/keys'
Release note: