Repository navigation
Replies: 3 comments 2 replies
|
Did you configure the post_logout_redirect_uri for the client? Did you also provide client_id or id_token_hint? |
|
Client configuration has post_logout_redirect_ur parameter filled with https://myurl/oidc/redirect To request the logout endpoint through POSTMAN : Authorization set on basic with Client_ID/Secret
id_token_hint parameter is for ID_Token not refresh token. I got in return Status 204 and the session to the RT is well disconnected because i am no more able to call UserInfo with the Access_Token If I change the redirection URL (which must be strictly identical to the one configured) I get the status 204 and I am well disconnected. I saw that RP-initiated logout was implemented in Keycloack recently, so, could the implementation be not complete ? |
|
Could be. Maybe have a look at the code to check if its actually supposed to do what you want? |
|
Unfortunately, as Identity Service Provider i have only POSTMAN to check the steps of the OIDC operation. The GET Deconnexion returns the expected code 200 |
|
does anybody has this issue ? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'm not sure but it seems that Keycloack is not fully compliant with RP-Initiated Logout as described in OpenID Connect RP-Initiated Logout 1.0.
When using POST method to diconnect user with the optionnal parameter post_logout_redirect_uri, this one is not taken.
User is well disconnected but not redirected to post_logout_redirect_uri instead of i get 204 status Code ( the request was successful but the client does not need to leave the current page).
It seems that keycloak can do this redirection (https://www.keycloak.org/docs/latest/server_admin/#rp-initiated-logout) although the method to use is not detailed. In doubt I suppose that it supports the 2 (GET and POST)
Am i wrong ?
thanks a lot
All reactions