Repository navigation
Mandatory redirect_uri in Pushed Authorization Requests (PAR) payload #36634
Unanswered
tomaskralik
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have a client that uses Pushed Authorization Requests to pass parameters using a back channel. However, it does not provide
redirect_uriin the PAR payload but rather passes it as a parameter when calling the authorization endpoint together withrequest_urireceived from the PAR endpoint.When I try to call Keycloak PAR endpoint without
redirect_uri, I get an errorI have gone through KC source code and it seems like
redirect_urialways has to be present in PAR request whenopenidscope is requested.I have also tried to pass some default
redirect_urihoping that theredirect_uriparam passed to authorization endpoint would override the value but to no avail. Client was redirected to URI passed in the PAR payload.Is there a way to accomodate the behaviour of this client apart from wrapping the both the PAR and authorization endpoint, aggregating the data and calling PAR endpoint once I have the
redirect_urivalue?Thank you for your time and advice.
All reactions