-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to provide client id during logoff #932
Comments
Related to #966 |
We can use an existing interface as param also on the logoff methods. Would be a breaking change. |
Hi @myronu The client_id is not an param used for the endsession endpoint. Why do you need this? What IdentityProvider do you use? Can you send me the specs of the endsession endpoint you use? Greetings Damien |
This is one of our company's main TID servers and is designed as a multi-tenant solution. I know it is based on Okta but I'm not sure if that parameter comes from Okta or something they added to facilitate redirecting to the correct server. |
There is another possibility that either logout is not being called properly, or the ID server is not handling it properly. Looking closer I see two calls being made, the first call looks like it includes the token but fails for some reason. The second call does not include the token and gives the error that client_id is not provided. |
Implemented, will be in Release 12. |
There is nothing in the documentation about calling logoff() with a url handler but it shows up as an optional parameter on the method. I am wondering how I could use that to provide additional parameters to the URL, specifically client_id. With our server I am receiving an error calling logout, "Invalid value for 'client_id' parameter."
The text was updated successfully, but these errors were encountered: