Applying the Patch to Configure Maximum Allowed Concurrent User Sessions
Describes the procedure to apply the patch to configure the maximum allowed concurrent sessions for Data Fabric users.
About this task
You can configure the maximum allowed number of concurrent sessions for Data Fabric users logging in to the Control System. By doing so, you can either restrict the number of concurrent user sessions or allow any number of concurrent sessions for Data Fabric users.
ATTENTION
You cannot perform a rolling upgrade to apply the
emergency bug fix (EBF) or patch to configure the maximum allowed number of
concurrent user sessions.Follow the steps given below to apply the EBF to configure the maximum allowed number of concurrent sessions for all Data Fabric users.
- Stop the
apiserver
service on all the cluster nodes on which theapiserver
service is running. - Apply the EBF/patch on all cluster nodes, after the
apiserver
service successfully stops running on the relevant cluster nodes. - If you wish to restrict the maximum concurrent user sessions, run the config save command to set the value for the
apiserver.max.concurrent.user.sessions
field. See config for details aboutapiserver.max.concurrent.user.sessions
. This is an optional step.TIPYou can run the config load command to confirm that the value of theapiserver.max.concurrent.user.sessions
has been set correctly. - Run
configure.sh
on all nodes. - Restart the
apiserver
service on the relevant cluster nodes that were previously running theapiserver
service.IMPORTANTIf you wish to restrict the maximum allowed concurrent user sessions, DO NOT configure spring security concurrency control in session-management. For example, DO NOT use code similar to the following:<session-management> <concurrency-control max-sessions="2" /> </session-management>