Closed soumyajose0784 closed 4 weeks ago
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
We have a requirement to pass an additional request parameter (which is not part of current OIDC configuration in pac4j-oidc) while hitting pingfederate authorization endpoint. The new parameter is a custom parameter added by client's authorization server
Could I get some advise on the best approach to handle it?
current: https:///as/authorization.oauth2?scope=openid+profile+email&response_type=code&redirect_uri=https:///druid-ext/druid-pac4j/callback&state=&client_id=Druid
New(new parameter AuthSource) https:///as/authorization.oauth2?AuthnSource=RefIdDruid&scope=openid+profile+email&response_type=code&redirect_uri=https:///druid-ext/druid-pac4j/callback&state=&client_id=Druid
Thanks Soumya
Thanks Soumya