Page History
...
- The following configuration items have to be added to the Controller instance's
private.conf
configuration file. For details see the JS7 - Controller Configuration Items article.- Mutual Authentication
Code Block language bash title Controller Configuration for Mutual Authentication linenumbers true js7 { auth { # User accounts for https connections users { # Controller account for connections by primary/secondary JOC Cockpit instance Controller { distinguished-names=[ "DNQ=SOS CA, CN=js7-joc-primary, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE", "DNQ=SOS CA, CN=js7-joc-secondary, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE" ] } } }
- This setting specifies the distinguished names which are available from the subjects of JOC Cockpit certificates. Note that the common name (CN) attribute specifies the hostname of a JOC Cockpit instance. The configuration authenticates a given JOC Cockpit instance as the distinguished name is unique for the server certificate and therefore replaces the use of passwords.
- Keystore and truststore locations:
Code Block language bash title Controller Configuration for Keystore and Truststore Locations linenumbers true js7 { web { # Locations of keystore and truststore files for HTTPS connections https { keystore { # Default: ${js7.config-directory}"/private/https-keystore.p12" file=${js7.config-directory}"/private/https-keystore.p12" key-password="jobscheduler" store-password="jobscheduler" } truststores=[ { # Default: ${js7.config-directory}"/private/https-truststore.p12" file=${js7.config-directory}"/private/https-truststore.p12" store-password="jobscheduler" } ] } } }
- The configuration items described above specify the locations of keystore and truststore.
- Note the optional use of a key password and store password for keystores and the use of a store password for truststores.
- Mutual Authentication
...
Overview
Content Tools