-
Notifications
You must be signed in to change notification settings - Fork 745
OIDC config to allow mismatched discovery / issuer #5712
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 config to allow mismatched discovery / issuer #5712
Conversation
14474be
to
d897dfb
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5712 +/- ##
==========================================
+ Coverage 58.49% 59.80% +1.31%
==========================================
Files 940 639 -301
Lines 71555 47344 -24211
==========================================
- Hits 41854 28316 -13538
+ Misses 26520 16916 -9604
+ Partials 3181 2112 -1069
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had a chat with @EngHabu. This pr is good to go thank you! There was some discussion about whether this config option needs to be piped in to the resource_server so that the issuer can be verified but it looks like we don't do that. In the self auth server case, the issuer is already read from config or matched against authorized urls so that's okay.
mind taking care of the checks though @ddl-ebrown |
d897dfb
to
4c5268d
Compare
- 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. - Regenerated flyteadmin code through mise with: mise x go@1.22 -- make generate Signed-off-by: ddl-ebrown <ethan.brown@dominodatalab.com>
4c5268d
to
662cec7
Compare
Code Review Agent Run #b5409eActionable Suggestions - 0Additional Suggestions - 1
Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
Changelist by BitoThis pull request implements the following key changes.
|
Tracking issue
Why are the changes needed?
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: oidc: add option to override discovered issuer URL 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.
Regenerated flyteadmin code through mise with:
What changes were proposed in this pull request?
How was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
This PR enhances Flyteadmin OIDC configuration by allowing separate issuer URLs for token validation. The changes update authentication context, configuration settings, and command flags to support issuer discrepancies. These updates address challenges with mismatched discovery URLs in environments like Azure or when using internal service addresses.Unit tests added: True
Estimated effort to review (1-5, lower is better): 1