Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oidc: add option to override discovered issuer URL #315

Merged
merged 1 commit into from
Sep 17, 2021

Conversation

ericchiang
Copy link
Collaborator

Fixes #250
Fixes #212

Copy link

@liafizan liafizan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We tried the fix in our environment where our OIDC connect provider has the issuer mismatch problem and this fix worked perfectly! Thank you for working on this

@ericchiang
Copy link
Collaborator Author

Glad this works for you! I think that's the feedback I need. Going to go ahead and merge.

@ericchiang ericchiang merged commit d42db69 into coreos:v3 Sep 17, 2021
@ericchiang ericchiang deleted the issuer branch September 17, 2021 00:06
ddl-ebrown added a commit to dominodatalab/flyte that referenced this pull request Aug 31, 2024
 - There are a number of cases where the OIDC discovery url returns one
   issuer, but its desirable to use a separately configured / named
   issuer for validation instead.

   There are cases in Azure where this is necessary due to their
   non-standard OIDC configuration -- which is why this was originally
   added:
   coreos/go-oidc#315

   There are also cases where it's necessary to use an in-cluster
   service address, but browser clients are using the external ingress
   address. Due to cluster DNS configuration, it's possible that
   flyteadmin may be unable to resolve or use the public ingress
   address for an Idp, but the internal service address is available.
   This configuration change allows for that.
ddl-ebrown added a commit to dominodatalab/flyte that referenced this pull request Aug 31, 2024
 - There are a number of cases where the OIDC discovery url returns one
   issuer, but its desirable to use a separately configured / named
   issuer for validation instead.

   There are cases in Azure where this is necessary due to their
   non-standard OIDC configuration -- which is why this was originally
   added:
   coreos/go-oidc#315

   There are also cases where it's necessary to use an in-cluster
   service address, but browser clients are using the external ingress
   address. Due to cluster DNS configuration, it's possible that
   flyteadmin may be unable to resolve or use the public ingress
   address for an Idp, but the internal service address is available.
   This configuration change allows for that.

Signed-off-by: ddl-ebrown <ethan.brown@dominodatalab.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issuer Name Mismatch Document Azure "{tenantid}" discovery quirks
2 participants