-
Notifications
You must be signed in to change notification settings - Fork 2k
Allow extra args to be provided to the OIDC auth endpoint #3034
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
Conversation
I meant this PR to have the "enhancement" label, but I'm not sure how that gets done. Is it possible to add the label after creation? |
Could you please open and link an issue and outline the problem there? |
2526b56
to
4d931ba
Compare
Codecov Report
@@ Coverage Diff @@
## main #3034 +/- ##
==========================================
- Coverage 51.58% 51.57% -0.02%
==========================================
Files 60 60
Lines 16675 16690 +15
==========================================
+ Hits 8602 8608 +6
- Misses 7783 7790 +7
- Partials 290 292 +2
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@alanwilkie-finocomp Our project depends an another repo for OIDC. I would recommend you open this on that specific project, which would allow us to bring over the features that are would be implemented. https://github.com/nginxinc/nginx-openid-connect Thank you. |
To clarify. We don't maintain a fork of the nginx openid connect project, but rather sync with it. The other changes are specific to this project. |
Thanks @jasonwilliams14 and @brianehlert, I'll have a look at nginx-openid-connect and see if I can get the JS changes into that codebase. |
The JS change has now been merged into nginx-openid-connect (nginxinc/nginx-openid-connect#67). |
Thank you. We will review on our side now that the changes have been merged into the OIDC project. |
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.
Just one small change
multiple arguments may be provided by concatenating them with
&
, for examplearg1=value1&arg2=value2
I think we want to use something like a list separated by ,
arg1=value1,arg2=value2
instead of &
in the YAML file. That would be more consistent with other parameters and YAML in general.
Then you can just replace ,
wit &
when you pass the string to the javascript.
Let me know what you think about it and if you have any questions.
Hi @lucacome Would it be better to make the arguments a YAML list? Like:
or:
|
Yeah, that's probably even better @alanwilkie-finocomp ! |
I've updated the PR with the new policy item as a list of strings that are concatenated with |
Proposed changes
Some OIDC Identity Providers provide extended capabilities by adding extra query string arguments to the authentication request. This change allows the OIDC policy to specify the extra arguments.
Specifically, Keycloak allows a default identity provider to be specified by adding a "kc_idp_hint" parameter to the authentication request (see https://www.keycloak.org/docs/latest/server_admin/#_client_suggested_idp).
Checklist
Before creating a PR, run through this checklist and mark each as complete.