...
Anchor | ||||
---|---|---|---|---|
|
JOC Cockpit Clusters
Display feature availability | ||
---|---|---|
|
Multiple instances of the JOC Cockpit can be synchronized to provide a high availability cluster. (This feature is available with Release 1.12.1 and newer)
To enable clustering of the JOC Cockpit:
...
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.
, active cluster that is transparent to the user and allows seamless fail-over.
A more detailed description can be found in the JOC Cockpit - Clustering article.
Cluster configuration is described in the Clustering section of the Authentication and Authorization - Configuration article
...
.
Implementation
- The JOC Cockpit uses Apache Shiro to authenticate and authorize users.
- Authentication and Authorization information can be read by Shiro from a number of separate resources. These are:
- a local configuration (
shiro.ini
) file that may include both authentication and authorization information, depending on the methods of authentication and authorization configured; - a authentication service that provides an LDAP interface such as Microsoft Active Directory and
- a database containing both authentication and authorization information and which complies with the Shiro data model requirements. This database will be managed (and populated) by a system administrator.
- a local configuration (
...