Page History

...

• The setting listed above applies for the connection established from one or more JOC Cockpit instances to a Controller. The JOC Cockpit can be used as a cluster comprising two or more instances.
• This setting specifies the distinguished-names indicated with the relevant JOC Cockpit's Client Authentication certificate. The certificate is considered a replacement for a password. For each JOC Cockpit instance, the distinguished name is specified which is stated in the JOC Cockpit's certificate.
• Two entries are available for js7.auth.users.History and js7.auth.users.JOC:
  • History represents the JS7 - History Service that receives state transition events for orders and log output of jobs and adds them to the JS7 database.
  • JOC represents the JOC Cockpit Proxy Service that establishes the connection to a Controller and which is used to provide current information about orders to the JOC Cockpit GUI, in addition to, for examplethe example the deployment of workflows and submission of orders.
  • For both History and JOC services a hashed password is specified by the JOC Cockpit. The password has no relevance for the security of the connection. Instead it is used to distinguish the services that both are running with the same JOC Cockpit instance and therefore use the same Client Authentication certificate.
• In addition permissions are specified for JOC Cockpit services that indicate with the UpdateItem setting that the JOC Cockpit service is allowed to add/update/delete deployable objects such as workflows.

...

See the JS7 - Agent Configuration Items#js7-web-https-keystore article for a an explanation of the setting.

...

See the JS7 - Agent Configuration Items#js7-configuration-trusted-signature-keys article for a an explanation of the setting.

...

See the JS7 - Agent Configuration Items#js7-job-execution-signed-script-injection-allowed article for a an explanation of the setting.

...