Closed xecollons closed 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Questions are community supported only and the authors/maintainers may or may not have time to reply. If you or your company would like commercial support, please see here for more information.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Hello,
I'm trying to log out a site using endsession endpoint with a post_logout_redirect_uri with params in the query. An example of this is this call:
http://myserver.com/connect/endsession?id_token_hint=xxx&post_logout_redirect_uri=https%3A%2F%2Fwww.myotherweb.com%2Fwithid%3FuserId%3D123
where I have a userId in my redirect uri.
This is throwing me an "Invalid PostLogoutRedirectUri". Without the params, it's working. What I would have in my PostLogoutUris list for this example is
https://www.myotherweb.com/withid
, without the params, of course. If we go to the OIDC specs, it saysSo I understand that query params are allowed. Looking at the IS4 source, I have arrived to the EndSessionRequestValidator and, after that, to StringCollectionContainsString, where, if I'm seeing it correctly (I may not), it's just comparing the uri as string, without removing it's params that it could have, with our registered PostLogoutUris list. Is that ok? Am I missing something? Shouldn't it just compare the non query parameters part?
Thanks.