Page History

...

• History
  • Settings in this section are used for the History Service of JOC Cockpit instances that access the given Controller.
  • distinguished-names
    • Specifies the distinguished name as given with the subject of the Client Authentication Certificate for incoming HTTPS connections of JOC Cockpit instances.
    • Any number of distinguished names can be specified allowing a number of incoming HTTPS connections from different JOC Cockpit instances.
    • Except for whitespace between attributes the precise sequence and values as available from the certificate's subject has have to match this property value.
    • Note that the common name (CN) element in the distinguished name has to match the fully qualified domain name (FQDN) of a JOC Cockpit instance's host.

    • The following command can be used to read the distinguished name from a certificate file:

      
      

      Code Block
      title Example for OpenSSL command to read a certificate's distinguished name
      # read distinguished name from the JOC Cockpit instance's certificate file (.crt) openssl x509 -in joc-primary.crt -noout -nameopt RFC2253 -subject # output is returned with a prefix "subject= " or similar that is not part of the distinguished name # subject= DNQ=SOS CA,CN=joc-2-0-primary,OU=IT,O=SOS,L=Berlin,ST=Berlin,C=DE

  • password
    • A default password is specified with the section joc of the JS7 - Settings page of JOC Cockpit and in the private.conf file. The password is used for authentication of the History service account with the Controller, for details see next chapter about password authentication.
    • The password setting cannot be omitted, however, an empty password can be specified like this:
      • password="plain:"
    • At the same time the password setting in JOC Cockpit has to be assigned an empty value.
• JOC
  • Settings in this section are used for services running in JOC Cockpit instances that access the given Controller.
  • distinguished-names:  The same applies as for the History setting described above.
  • permissions: JOC Cockpit requires the UpdateItem permission to enable users to deploy objects such as workflows.
  • password: The same applies as for the History setting described above.

...