soumyajose0784 opened a new issue #11851: URL: https://github.com/apache/druid/issues/11851
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://<pingfedserver>/as/authorization.oauth2?scope=openid+profile+email&response_type=code&redirect_uri=https://<druid_router_address>/druid-ext/druid-pac4j/callback&state=<statevalue>&client_id=Druid **New(new parameter AuthSource)** https://<pingfedserver>/as/authorization.oauth2?AuthnSource=RefIdDruid&scope=openid+profile+email&response_type=code&redirect_uri=https://<druid_router_address>/druid-ext/druid-pac4j/callback&state=<statevalue>&client_id=Druid Thanks Soumya Thanks Soumya -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
