What is the best approach to logout from keycloak after authentication via pkce?

user_4461271 0
Viewed 1762

What is the proper way to logout?

These are the keycloak client settings:

Realm: REALM

Client ID:              pkce-client
Client Protocol:        openid-connect
Access Type:            public
Standard Flow Enabled:  ON
Valid Redirect URIs:    http://localhost:4200/
Backchannel Logou:      ON

OpenID Connect Compatibility Modes

Use Refresh Tokens: ON

Advanced Settings:

Proof Key for Code Exchange Code Challenge Method: S256

Is there a good documentation?

My idea was to delete the token on the client side, but then the session is still active in keycloak.

The solution was to call the following URL:

http://localhost:8180/auth/realms/REALM/protocol/openid-connect/logout?id_token_hint=InR5cCIgOiAiSldUIiwia2lkIiA6ICIxUVJwMXAtbmk1WmcyZmlyRHFoRS1iS1hwemZDaWFocGs4Zi1XRkQtRDZ3In0.eyJleHAiOjE2NDE3NjUyNjYsImlhdCI6MTY0MTc2.......
pkce keycloak openid-connect logout
3 Answers

OIDC standard (implemented by Keycloak) supports RP initiated logout. So make browser redirect (not a XMLHttpRequest request only) to end_session_endpoint with proper logout parameters.

BTW: end_session_endpoint is not the same as revocation_endpoint; logout != revocation.

But this is OIDC logout only (logout from the Keycloak). You may have still own app session (it depends on the app implementation), so app needs to destroy app session ("delete refresh token on the client side", ...) to have logout from the app.

user_33486040

You can create a logout service backend that you make available on /logout endpoints of all your services.

When the service is called, it first obtains the ID token for the client used to connect:

curl -k  https://<keycloak-host>/auth/realms/<realm>/protocol/openid-connect/token \
  -d "grant_type=client_credentials" \
  -d "client_id=<client-id>" \
  -d "client_secret=<secret>" \
  -d "scope=openid"

See this answer.

Then it constructs a redirect URL in a format like this based on host of user:

https://<host>?cache-buster=1445660571

With an optional cache buster.

Create a redirect URL to the authorization server in this format:

https:///auth/realms//protocol/openid-connect/logout?id_token_hint=&post_logout_redirect_uri=<url encoded redirect URL>

Then create a response with status code 303 (See Other) with as Location the URL constructed above, and as headers you set the "kc-access", "kc-state", "OAuth_Token_Request_State" and "request_uri" cookies to expired. Clojure example:

(defn- expired-cookie [host cookie-name]
  (str cookie-name "=; "
       "domain=." host "; "
       "path=/; "
       "expires=Thu, 01 Jan 1970 00:00:00 GMT; "
       "HttpOnly"))

Example response:

status: 303
headers: 
{"Location" "https://<keycloak host>/auth/realms/<realm>/protocol/openid-connect/logout
?id_token_hint=<id token you obtained>
&post_logout_redirect_uri=<url encoded redirect URL>"
 "Set-Cookie" 
["kc-access=; domain=.https://<domain>; path=/; 
  expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly"
 "kc-state=; domain=.https://<domain>; path=/; 
  expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly"
 "OAuth_Token_Request_State=; domain=.https://<domain>; path=/; 
  expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly"
 "request_uri=; domain=.https://<domain>; path=/; 
  expires=Thu, 01 Jan 1970 00:00:00 GMT; HttpOnly"]}

This returned response will log the user out and redirect to the constructed redirect URL (for example, where the user came from).

This /logout endpoint can be made available as a route on all services that use Keycloak.

user_26099800

The solution was to call the following URL:

http://localhost:8180/auth/realms/REALM/protocol/openid-connect/logout?id_token_hint=InR5cCIgOiAiSldUIiwia2lkIiA6ICIxUVJwMXAtbmk1WmcyZmlyRHFoRS1iS1hwemZDaWFocGs4Zi1XRkQtRDZ3In0.eyJleHAiOjE2NDE3NjUyNjYsImlhdCI6MTY0MTc2.......
user_44612710
Related