Keycloak creates a session of camunda-identity-service client during spring boot application startup

[bolatk]

Hi! First of all, thank you @VonDerBeck for such useful plugin. I need your help with session issue.
I have a camunda-identity-service client and another client with access type public for my Vuejs application. When I login to my Vuejs application with Keycloak login page, I am able to automatically login to Camunda web app because of SSO. Then, when I logout from Camunda web app, I am also automatically logout from Vuejs. All sessions destroy in Keycloak Session web page.
But if I logout within Vuejs application, Camunda web app remains active, because there is the active session in Keycloak Session web page, which was created when Spring boot application start up.
So, why camunda identity plugin creates a new session during Spring boot application starts up? How to solve the session issue?
Thank you in advance.

[VonDerBeck]

Hi @bolatk,

the Camunda Keycloak SSO example is what it says - it is an example. Within this project the logout of Camunda involves the logout from Keycloak itself - see the implementation of the LogoutHandler. Furthermore this behaviour has nothing to do with the KeycloakIdentityProvider Plugin itself - this is part of standard Spring Security. The sample shows how to integrate both worlds in order to have it all. Please adapt the behaviour to your own needs - e.g. remove or replace the LogoutHandler functionality if you do not want that part of the example.

Does this help?

[bolatk]

Thank you for your help @VonDerBeck