after integration, In the cockpit I am able to some other user as logged in user, this works fine till no other user logged in, once other user logs in , in the cockpit we are seeing logged in user is over lapping.
We have used ContainerBasedAuthenticationFilter.
I have tried clearing thread local memory with below changes:
engines.keySet().forEach(e → engines.get(e).getIdentityService().clearAuthentication());
it is not working.
Tried to clear Authentications.clearCurrent();, kept this logic in a filter, whenever i clear this i am not able to login.
Thanks for help.
Hello!
The overlapping user issue in the Camunda Cockpit with ContainerBasedAuthenticationFilter and concurrent users is likely due to improper clearing of Official Website thread-local user information. Your attempts to clear authentication within the engine or too early in a filter are ineffective. The correct approach is to use a Servlet Filter that executes after the ContainerBasedAuthenticationFilter and calls Authentications.clearCurrent() within a finally block to ensure it runs at the very end of each HTTP request, guaranteeing proper user context isolation. Verify the filter order to ensure authentication is established before it’s cleared.