Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12, 1.13
-
None
Description
Current Situation
When running JOC in a JOC cluster with
sessionDAO = com.sos.auth.shiro.SOSDistributedSessionDAO securityManager.sessionManager.sessionDAO = $sessionDAO
and executing a logout the related session is still available on instances that are related to the session.
Desired Behavior
When executing a logout in a JOC cluster all related instances should no longer be able to use this logged out session.
How to reproduce
call attached script with
$ ./joc_cockpit_cluster_check.sh -is-de -a$(<cred) -uhttp://host1:4446 -rhttp://host2:4446 -t20
Patch
A patch is available here
Please note that this patch contains all other patches for JOC 1.13.3
Attachments
Issue Links
- links to