You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Although OpenId Discovery endpoint does not require request parameters however there is, at least one OAuth2 provider (azure), which requires them, or at least, when the tokens are digitally signed with a signing key issued for one application/tenant.
At the moment, RabbitMQ does not allow users configure any request parameter for the OpenID discovery endpoint. For users wanted to use Azure as their OAuth2 server, they have to discover the jwks url and configure RabbitMQ accordingly.
This is really a work around
Describe the solution you'd like
The solution is to allow users to configure the request parameters sent to the OpenId discovery endpoint so that users do not have to manually configure their jwks url but only the issuer url.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Although OpenId Discovery endpoint does not require request parameters however there is, at least one OAuth2 provider (azure), which requires them, or at least, when the tokens are digitally signed with a signing key issued for one application/tenant.
At the moment, RabbitMQ does not allow users configure any request parameter for the OpenID discovery endpoint. For users wanted to use Azure as their OAuth2 server, they have to discover the jwks url and configure RabbitMQ accordingly.
This is really a work around
Describe the solution you'd like
The solution is to allow users to configure the request parameters sent to the OpenId discovery endpoint so that users do not have to manually configure their jwks url but only the issuer url.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: