feat: experimental CORS proxy for OIDC #460
Merged
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.
The CORS proxy feature is experimental for use by deployments unable to control their OIDC Provider's CORS policy. The web client (UI) is configured to use the CORS proxy by setting:
The CORS proxy forwards incoming requests to the OIDC Provider configured by
STIGMAN_OIDC_PROVIDER
Adds endpoints:
Adds optional envvar:
STIGMAN_OIDC_PROXY_HOST: No default The
Host:
header value to be used by the CORS proxy for outbound requests. Some OIDC providers return configuration metadata with endpoint URLs having this value as their base.