Description of problem: Currently when loading up additional hosts in a JVM cluster, it is common that the administrator forgets to copy the secret key file across from the other hosts. Thus it is generated afresh upon startup leading to mysterious problems with the user suddenly becoming logged out (when they happen to get switched over to a different server in the cluster). The secret key should be synchronnized across servers, preferrably be storing it in the DB. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: See also bug 103295 which could be addressed at the same time for minimal extra work.
Fixed on the trunk with change 39030. This lead to some changes in how we register security providers. Updated the install guide to reflect the new way of doing things in changes 39034 and 39115. See bug #103295 for more details.