Page History

...

The configuration of the shiro.ini file for use with LDAP Authentication is described in the LDAP Configuration article.

Clustering

Multiple instances of the JOC Cockpit can be configured to operate as an active cluster. This requires a load balancer and session sharing between the JOC Cockpit instances. See the JOC Cockpit - Authentication and Authorization article for an introduction to Clustering.

Clustering is configured as follows:

• Install two or more instances of the JOC Cockpit on separate servers.
• All JOC Cockpit servers must use the same reporting database.

• Add the following two lines of code to the [main] section of the Shiro configuration for one of the instances:

  Code Block
  language xml
  sessionDAO = com.sos.auth.shiro.SOSDistributedSessionDAO securityManager.sessionManager.sessionDAO = $sessionDAO

  This can be done most easily using the Enable JOC Cluster button in the Manage Accounts / Main Section tab.

• Connect all JOC Cockpit servers to a load balancer.

Database Authentication

System administrators can implement database authentication manually, using a separate database to the JobScheduler(s) and, if required, a separate DBMS.

...