Keystore and truststore in orange color are required for any connections of JOC Cockpit to a Controller.
- The Controller's private key and certificate for Server Authentication are added to the Controller's keystore. In case of a self-signed certificate the certificate is added to the JOC Cockpit truststore as well.
- This step can be skipped if a CA-signed certificate is used as the Root Certificate in the JOC Cockpit truststore is sufficient to verify Controller certificates.
Keystore and truststore in green color are required if mutual authentication is in place for certificate based client authentication (default).
A Controller truststore in green color is required should secure connections be used by a Controller to access Agents. It is therefore recommended to set up the Controller truststore.

Secure Connection Setup

This configuration is applied in order to secure the connection if JOC Cockpit and Controller are not operated on the same server. If not otherwise stated then the steps for HTTPS configuration are performed on the server that hosts the Controller.

Step 1: Create the Keystore

...

In the following the placeholders JOC_HOME, JETTY_HOME and JETTY_BASE are used which locate three directories. If you install Jetty with the JOC Cockpit installer then

JOC_HOME is the installation path that is specified during JOC Cockpit installation:
- /opt/sos-berlin.com/js7/joc (default on Linux)
- C:\Program Files\sos-berlin.com\js7\joc (default on Windows)
JETTY_HOME = JOC_HOME/jetty
JETTY_BASE is Jetty's base directory that is specified during JOC Cockpit installation:
- /home/<setup-user>/sos-berlin.com/js7/joc (default on Linux)
- C:\ProgramData\sos-berlin.com\js7\joc (default on Windows)

For Controller instances the following placeholders are used:

JS7_CONTROLLER_HOME points to the Controller instance's installation directory
- /opt/sos-berlin.com/js7/controller (default on Linux)
- C:\Program Files\sos-berlin.com\js7\controller (default on Windows)
JS7_CONTROLLER_CONFIG_DIR points to the Controller instance's configuration directory
- /var/sos-berlin.com/js7/controller/config (default on Linux)
- C:\ProgramData\sos-berlin.com\js7\config (default on Windows)

Secure Connections for JOC Cockpit to Controller

This configuration is applied in order to secure the connection if JOC Cockpit and Controller are not operated on the same server and network interface.

Secure connections require authentication.

By default JOC Cockpit and Controller use mutual authentication:
- JOC Cockpit verifies the Controller certificate for Server Authentication.
- Controller verifies the JOC Cockpit certificate for Client Authentication.
- For details JS7 - Configuration for mutual HTTPS Server Authentication and Client Authentication.
If mutual authentication cannot be applied, e.g. in case of use with wildcard certificates:
- Consider to use password based authentication.
- For details see JS7 - Configuration for HTTPS Server Authentication with Passwords.

For the complete list of related configuration items see JS7 - Controller Configuration Items.

The following chapters assume mutual authentication to be in place.

Step 1: Create the Controller Keystore

On the Controller instance's server create the keystore using the keytool from your Java JRE or JDK or some third party utility.

For use with a third party utility create a keystore, e.g. https-keystore.p12, in PKCS12 format and import:
- Controller private key and certificate for Server Authentication
- Root CA certificate
- Intermediate CA certificates

Generate the keystore with the private key and the certificate for Controller Server Authentication. The below examples suggest one possible approach for certificate management, however, there may be other ways how to achieve similar results.

Example for use of CA-signed certificate with PKCS12 keystore format

Code Block

language	bash
title	Example how to add a CA-signed private key and certificate to a PKCS12 Keystore

# should the Controller's private key and certificate be provided with a .jks keystore (keypair.jks) then temporarily convert the keystore to pkcs12 (keystore.p12)
#   for later use with openssl, assuming the alias name of the Controller private key being "controller-https"
# keytool -importkeystore -srckeystore keypair.jks -destkeystore keystore.p12 -deststoretype PKCS12 -srcalias controller-https

# assuming the Controller's private key from a pkcs12 keystore (keystore.p12), store the Controller's private key to a .key file in PEM format (controller-https.key)
openssl pkcs12 -in keystore.p12 -nocerts -out controller-https.key

# concatenate CA Root certificate and CA Intermediate certificate to a single CA Bundle certificate file (ca-bundle.crt)
cat RootCACertificate.crt > ca-bundle.crt
cat CACertificate.crt >> ca-bundle.crt

# Export Controller's private key (controller-https.key), Controller's certificate (controller-https.crt) and CA Bundle (ca-bundle.crt) in PEM format to a new keystore (https-keystore.p12)
#   assume the fully qualified hostname (FQDN) of the Controller server being "controller.example.com"
openssl pkcs12 -export -in controller-https.crt -inkey controller-https.key -chain -CAfile ca-bundle.crt -name controller.example.com -out JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12

# should you require use of a .jks keystore type then convert the pkcs12 keystore assuming the alias name of the Controller private key being "controller-https"
# keytool -importkeystore -srckeystore https-keystore.p12 -srcstoretype PKCS12 -destkeystore https-keystore.jks -deststoretype JKS -srcalias controller-https

Example for use of self-signed certificate with PKCS12 keystore format

Code Block

language	bash
title	Example how to generate a self-signed certificate for import into a PKCS12 Keystore

# generate Controller's private key with alias name "controller-https" in a keystore (https-keystore.p12)
#   use the fully qualified hostname (FQDN) and name of your organization for the distinguished name
#   consider that PKCS12 keystores require to use the same key password and store password
keytool -genkey -alias "controller-https" -dname "CN=hostname,O=organization" -validity 1461 -keyalg RSA -keysize 2048 -keypass jobscheduler -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.pk12" -storepass jobscheduler -storetype PKCS12

Example for use of self-signed certificate with JKS keystore format

Code Block

language	bash
title	Example how to generate a self-signed private key and certificate for import into a JKS Keystore

# generate Controller's private key with alias name "controller-https" in a keystore (https-keystore.jks)
#   use the fully qualified hostname (FQDN) and name of your organization for the distinguished name
keytool -genkey -alias "controller-https" -dname "CN=hostname,O=organization" -validity 1461 -keyalg RSA -keysize 2048 -keypass jobscheduler -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.jks" -storepass jobscheduler

Explanation:
- Replace the JS7_CONTROLLER_CONFIG_DIR placeholder as specified above.
- The -dname option specifies the certificate issuer, therefore use your own set of CN, O, OU, DC that specify the issuer's distinguished name. The O setting is required for the issuer.
- The -keypass option accepts the password that you will need later on to manage your private key. With the default password being used no further settings are required as explained below.
- The -keystore option specifies the location of the keystore file. The keystore file should be in reach of the Controller, it is recommended to use the sub-folder private in the JS7_CONTROLLER_CONFIG_DIR directory.
- The -storepass option specifies the password for access to the keystore file. For the handling of the default password the same applies as stated with the -keypass option.
- The -storetype option is used to specify the PKCS12 keystore format or JKS keystore format.

With the keystore being set up specify respective properties with the JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file:

Example

Code Block

language	text
title	Example for private.conf file specifying the Controller keystore

js7 {
    web {
        # keystore location 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
            }
        }
    }

Explanation:

js7.web.https.keystore.file is used for the path to the keystore.
js7.web.https.keystore.key-password is used for access to the private key.
js7.web.https.keystore.store-password is used for access to the keystore.

Step 2: Set up Authentication to Controller

By default mutual authentication is in place.
- JOC Cockpit is challenged by the Controller to present its Client Authentication certificate that is verified by the Controller.
  - In addition the distinguished name of the JOC Cockpit Client Authentication is checked and a password is used to identify the JOC Cockpit instance.
  - Consider that any number of clustered JOC Cockpit instances can connect to a Controller.
- If a Controller cluster is used then connections from the partnering Controller instance are authenticated by instance's Client Authentication distinguished name.

The JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file is authentication details like this:

Code Block

title	Example for private.conf file specifying JOC Cockpit authentication

js7 {
    auth {
        users {
            # History account (used for release events)
            History {
                distinguished-names=[
                    "DNQ=SOS CA, CN=apmacwin_joc_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
                password="sha512:B793649879D61613FD3F711B68F7FF3DB19F2FE2D2C136E8523ABC87612219D5AECB4A09035AD88D544E227400A0A56F02BC990CF0D4CB348F8413DE00BCBF08"
            }
            # JOC account (needs UpdateItem permission for deployment)
            JOC {
                distinguished-names=[
                    "DNQ=SOS CA, CN=apmacwin_joc_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
                password="sha512:3662FD6BF84C6B8385FC15F66A137AB75C755147A81CC7AE64092BFE8A18723A7C049D459AB35C059B78FD6028BB61DCFC55801AE3894D2B52401643F17A07FE"
                permissions=[
                    UpdateItem
                ]
            }
            # Controller ID for connections by primary/secondary controller instance
            jobscheduler {
                distinguished-names=[
                    "DNQ=SOS CA, CN=apmacwin_secondary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
            }
        }
    }
}

Explanation:

The History and JOC user accounts are used by the JS7 - History Service and by the JS7 - REST Web Service API.
- The distinguished-names property offers to add a number of distinguished names available from the subject of the respective Client Authentication certificate.
- The password is not used for authentication but for identification of the History and JOC user accounts as both accounts typically are running in the same JOC Cockpit instance and use the same Client Authentication certificate. When used with HTTP connections then the password is used for authentication.
The jobscheduler user account is an example for a Controller ID as used by a partnering Controller instance.
- This setting is not required if a standalone Controller is used.
- For a Controller cluster the Controller ID is specified during installation.

Step 3: Set up the Controller Instance Start Script for HTTPS

To make a Controller use HTTPS the respective port setting has to be specified with the Controller's JS7_CONTROLLER_HOME/bin/controller_instance Instance Start Script like this:

Code Block

language	xml

rem # Sets the http port for the JS7 Controller.
rem # Without this setting the default port 4444 is used.
rem # If just a port is specified then the JS7 Controller listens to all
rem # available network interfaces. This corresponds to 0.0.0.0:<port>.
rem # Use the form <ip address or hostname>:<port> to indicate
rem # a specific network interface the JS7 Controller should listen to.
rem # The command line option --http-port beats the environment
rem # variable JS7_CONTROLLER_HTTP_PORT.

set JS7_CONTROLLER_HTTP_PORT=localhost:4444


rem # In addition to the http port an https port for the
rem # JS7 Controller can be specified. If just a port is specified
rem # then the JS7 Controller listens to all available network interfaces.
rem # This corresponds to using 0.0.0.0:<port>.
rem # Use the form <ip address or hostname>:<port> to indicate
rem # a specific network interface the JS7 Controller should listen to.
rem # The command line option --https-port beats the environment
rem # variable JS7_CONTROLLER_HTTPS_PORT.

set JS7_CONTROLLER_HTTPS_PORT=apmacwin:4444

Explanation:

The HTTP port is required but is limited to the localhost network interface with the localhost prefix.
The HTTPS port is specified with the hostname prefix that indicates the network interface.

Step 4: Configure the JOC Cockpit Truststore

On the JOC Cockpit server perform the following steps:

The JOC Cockpit truststore is added the Root CA certificate. If self-signed certificates are used then each certificate is added to the JOC Cockpit truststore.

Example for import of a Root CA certificate to a PKCS12 truststore:

Code Block

language	bash
title	Example how to import a CA signed certificate into a PKCS12 Truststore

# import Root CA certificate in PEM format to a PKCS12 truststore (https-truststore.p12)
keytool -import -alias "root-ca" -file "RootCACertificate.crt" -keystore "JETTY_BASE/resources/joc/https-truststore.p12"

Example for use of a self-signed Controller certificate with a JOC Cockpit PKCS12 truststore:

Code Block

language	bash
title	Example for import of a self-signed Controller certificate the Master public certificate to JOC Cockpit PKCS12 Truststore

# import Master public certificate from a file in PEM format (master-https.crt) identified by its alias name (master-https) to the JOC Cockpit PKCS12 keystore (joc-https.p12)
keytool -importcert -noprompt -file "master-https.crt" -alias "master-https" -keystore "JETTY_BASE/etc/joc-https.p12" -storepass jobscheduler -storetype PKCS12 -trustcacerts

Example for use of a self-signed Controller certificate with a JOC Cockpit JKS truststore:

Code Block

language	bash
title	Example for import of a self-signed Controller certificate the Master public certificate to JOC Cockpit JKS Truststore

# import Master public certificate from a file in PEM format (master-https.crt) identified by its alias name (master-https) to the JOC Cockpit JKS keystore (joc-https.jks)
keytool -importcert -noprompt -file "master-https.crt" -alias "master-https" -keystore "JETTY_BASE/etc/joc-https.jks" -storepass jobscheduler -trustcacerts

The location of the truststore is added to the JETTY_BASE/resources/joc/joc.properties configuration file like this:

Example for PKCS12 keystore

Code Block

language	text

### Location of the Java truststore that contains the certificates of all
###   Controllers used for HTTPS connections. The path can be absolute or
###   relative to joc.properties

truststore_path = ../../resources/joc/https-truststore.p12 
truststore_type = PKCS12
truststore_password = jobscheduler

Example for JKS keystore

Code Block

language	text

### Location of the Java truststore that contains the certificates of all
###   Controllers used for HTTPS connections. The path can be absolute or 
###   relative to joc.properties

truststore_path = ../../resources/joc/https-truststore.jks
truststore_type = JKS
truststore_password = jobscheduler

Hostname verification by default is in place with

...

create a keystore, e.g. https-keystore.p12, in PKCS12 format and import:
- Controller private key and certificate
- Root CA certificate
- Intermediate CA certificates
create a truststore, e.g. https-truststore.p12, in PKCS12 format and import:
- Root CA certificate

...

Code Block

language	bash
title	Example how to add a CA signed private key and certificate to a PKCS12 Keystore

# should the Controller's private key and certificate be provided with a .jks keystore (keypair.jks) then temporarily convert the keystore to pkcs12 (keystore.p12)
#   for later use with openssl, assuming the alias name of the Controller private key being "controller-https"
# keytool -importkeystore -srckeystore keypair.jks -destkeystore keystore.p12 -deststoretype PKCS12 -srcalias controller-https

# assuming the Controller's private key from a pkcs12 keystore (keystore.p12), store the Controller private key to a .key file in PEM format (controller-https.key)
openssl pkcs12 -in keystore.p12 -nocerts -out controller-https.key

# concatenate CA Root certificate and CA Intermediate certificate to a single CA Bundle certificate file (ca-bundle.crt)
cat RootCACertificate.crt > ca-bundle.crt
cat CACertificate.crt >> ca-bundle.crt

# Export Controller private key (controller-https.key), Controller certificate (controller-https.crt) and CA Bundle (ca-bundle.crt) in PEM format to a new keystore (https-keystore.p12)
#   assume the fully qualified hostname (FQDN) of the Controller server being "controller.example.com"
openssl pkcs12 -export -in controller-https.crt -inkey controller-https.key -chain -CAfile ca-bundle.crt -name controller.example.com -out https-keystore.p12

# should you require use of a .jks keystore type then convert the pkcs12 keystore assuming the alias name of the Controller private key being "controller-https"
# keytool -importkeystore -srckeystore https-keystore.p12 -srcstoretype PKCS12 -destkeystore https-keystore.jks -deststoretype JKS -srcalias controller-https

...

Example for use of self-signed certificate with PKCS12 keystore format

Code Block

language	bash
title	Example how to generate a self-signed certificate for import into a PKCS12 Keystore

# generate Controller's private key with alias name "controller-https" in a keystore (https-keystore.p12)
#   use the fully qualified hostname (FQDN) and name of your organization for the distinguished name
#   consider that PKCS12 keystores require to use the same key password and store password
keytool -genkey -alias "controller-https" -dname "CN=hostname,O=organization" -validity 1461 -keyalg RSA -keysize 2048 -keypass jobscheduler -keystore "https-keystore.pk12" -storepass jobscheduler -storetype PKCS12

...

Example for use of self-signed certificate with JKS keystore format

Code Block

language	bash
title	Example how to generate a self-signed private key and certificate for import into a JKS Keystore

# generate Controller's private key with alias name "controller-https" in a keystore (https-keystore.jks)
#   use the fully qualified hostname (FQDN) and name of your organization for the distinguished name
keytool -genkey -alias "controller-https" -dname "CN=hostname,O=organization" -validity 1461 -keyalg RSA -keysize 2048 -keypass jobscheduler -keystore "https-keystore.jks" -storepass jobscheduler

...

Explanations

Replace the SCHEDULER_DATA placeholder as specified above.
The -dname option specifies the certificate issuer, therefore use your own set of CN, O, OU, DC that specify the issuer's distinguished name. The O setting is required for the issuer.
The -keypass option accepts the password that you will need later on to manage your private key. With the default password being used no further settings are required as explained below.
The -keystore option specifies the location of your Keystore file.
- The Keystore file should be in reach of the JobScheduler Master, it is therefore recommended to use a sub-folder private in the ./config directory.
- Using the default file name "private-https.jks" will save the effort of adding further settings as explained above.
The -storepass option specifies the password for access to your Keystore file. For the handling of the default password the same applies as stated with the -keypass option.
The -storetype option is used for the PKCS12 keystore format, this option is not required for the JKS keystore format.

...

Explanations
- jobscheduler.master.webserver.https.keystore.file is used for the path to the Keystore
- jobscheduler.master.webserver.https.keystore.password is used for the Keystore password
- jobscheduler.master.webserver.https.keystore.key-password is used for the password of your private key

Example

Code Block

language	text
title	Example for private.conf file specifying the Master Keystore

jobscheduler.master.webserver.https.keystore {
  file = "C:/ProgramData/sos-berlin.com/jobscheduler/master110/config/private/private-https.jks"
  # Backslashes are written twice (as in JSON notation):
  # file = "\\\\other-computer\\share\\my-keystore.jks"
  password = "jobscheduler"
  key-password = "jobscheduler"
}

...

Example for export with JKS keystore format

Code Block

language	bash
title	Example how to export the Master public certificate from a JKS Keystore

# export Master public certificate from keystore (private-https.jks) identified by its alias name (master-https) to a file in PEM format (master-https.crt)
keytool -exportcert -rfc -noprompt -file "master-https.crt" -alias "master-https" -keystore "SCHEDULER_DATA/config/private/private-https.jks" -storepass jobscheduler

Example for export with PKCS12 keystore format

Code Block

language	bash
title	Example how to export the Master public certificate from a PKCS12 Keystore

# export Master public certificate from keystore (private-https.p12) identified by its alias name (master-https) to a file in PEM format (master-https.crt)
keytool -exportcert -rfc -noprompt -file "master-https.crt" -alias "master-https" -keystore "SCHEDULER_DATA/config/private/private-https.p12" -storepass jobscheduler -storetype PKCS12

The exported public certificate of each JobScheduler Master has to be imported to the Java Truststore that is used by the JOC Cockpit.

Step 2: Set up Authentication to Controller

The JobScheduler Master HTTPS web service is only accessible to authenticated users that are identified by the JobScheduler ID.
- The JobScheduler ID is specified on installation of a JobScheduler Master and is a unique string.
- Should you operate a JobScheduler cluster then the same JobScheduler ID is used that has been assigned to all Masters during setup. Do not mix up the JobScheduler ID and the suffix -backup that is applied to a Backup Master installation directory.
The JobScheduler Master expects HTTP Basic Authentication.
The credentials are used from SCHEDULER_DATA/config/private/private.conf configuration file that offers an entry like this:
Code Block
jobscheduler.master.auth.users { JOBSCHEDULER_ID = "HASH_SCHEME:HASHED_PASSWORD" }
The HASH_SCHEME is specified by the prefix "plain" and is followed by the password:
Code Block
jobscheduler.master.auth.users { jobscheduler_prod = "plain:secret" }

Step 3: Set up the Controller for HTTPS

Specify the ports with the <config> element in the SCHEDULER_DATA/config/scheduler.xml configuration file like this:

the HTTP port is required but is limited to the localhost network interface with the http_port attribute

the HTTPS port with the https_port attribute of like this:

Code Block

language	xml

<spooler>
        <config http_port="localhost:40444" https_port="48444" mail_xslt_stylesheet="config/scheduler_mail.xsl">
                <!-- other elements -->
        </config>
</spooler>

Step 4: Configure the JOC Cockpit Truststore

On the JOC Cockpit server perform the following steps:

The JOC Cockpit Keystore can also be used as a Truststore where the certificates of a number of JobScheduler Masters are imported.

Example for PKCS12 Keystore

Code Block

language	bash
title	Example how to import the Master public certificate to JOC Cockpit PKCS12 Keystore

# import Master public certificate from a file in PEM format (master-https.crt) identified by its alias name (master-https) to the JOC Cockpit PKCS12 keystore (joc-https.p12)
keytool -importcert -noprompt -file "master-https.crt" -alias "master-https" -keystore "JETTY_BASE/etc/joc-https.p12" -storepass jobscheduler -storetype PKCS12 -trustcacerts

Example for JKS Keystore

Code Block

language	bash
title	Example how to import the Master public certificate to JOC Cockpit JKS Keystore

# import Master public certificate from a file in PEM format (master-https.crt) identified by its alias name (master-https) to the JOC Cockpit JKS keystore (joc-https.jks)
keytool -importcert -noprompt -file "master-https.crt" -alias "master-https" -keystore "JETTY_BASE/etc/joc-https.jks" -storepass jobscheduler -trustcacerts

Explanation:
- The alias names of any certificates have to be unique for the target Keystore.
Alternatively, you can import the JobScheduler Master certificates into the default Java Truststore (JAVA_HOME/lib/security/cacerts) of the Java installation which is used by Jetty, however, this setting will be lost if you switch the Java version.

If you use the Keystore of your JOC Cockpit Web Service in Jetty as the Truststore of the JobScheduler Master certificates then add the location of the Truststore to the JETTY_BASE/resources/joc/joc.properties configuration file like this:
Example for PKCS12 keystore format
configuration file.
Code Block
language text
################################################################################ ###
Location
Should
of
hostname
the
verification
Java
be carried out for https certificate. ### Default false https_with_hostname_verification = true

Mutual Authentication for JOC Cockpit to Controller

This configuration is applied in order to enable mutual authentication:

JOC Cockpit verifies the Controller certificate for Server Authentication
Controller verifies the JOC Cockpit certificate for Client Authentication

Step 1: Create Controller Trusstore

For use with self-signed certiExport the JobScheduler Master public certificate for use with the JOC Cockpit Web Service

Example for export with

truststore that contains the certificates of all ### Controllers used for HTTPS connections. The path can be absolute or ### relative to joc.properties truststore_path = ../../resources/joc/https-truststore.p12 truststore_type = PKCS12 truststore_password = jobscheduler

Example for JKS keystore format

Code Block

language	text

### Location of the Java truststore that contains the certificates of all
###   Controllers used for HTTPS connections. The path can be absolute or 
###   relative to joc.properties

truststore_path = ../../resources/joc/https-truststore.jks
truststore_type = JKS
truststore_password = jobscheduler

Explanations
- The relative path from the above example looks up the Keystore in the JETTY_BASE/etc directory.

The hostname verification can be added optionally in the JETTY_BASE/resources/joc/joc.properties configuration file.

Code Block

################################################################################
### Should hostname verification be carried out for https certificate. 
### Default false

https_with_hostname_verification = true

Notes

	bash
title	Example how to export the Master public certificate from a JKS Keystore

# export Master public certificate from keystore (private-https.jks) identified by its alias name (master-https) to a file in PEM format (master-https.crt)
keytool -exportcert -rfc -noprompt -file "master-https.crt" -alias "master-https" -keystore "SCHEDULER_DATA/config/private/private-https.jks" -storepass jobscheduler

Example for export with PKCS12 keystore format

Code Block

language	bash
title	Example how to export the Master public certificate from a PKCS12 Keystore

# export Master public certificate from keystore (private-https.p12) identified by its alias name (master-https) to a file in PEM format (master-https.crt)
keytool -exportcert -rfc -noprompt -file "master-https.crt" -alias "master-https" -keystore "SCHEDULER_DATA/config/private/private-https.p12" -storepass jobscheduler -storetype PKCS12

The exported public certificate of each JobScheduler Master has to be imported to the Java Truststore that is used by the JOC Cockpit.

Notes

A restart of the respective component is required to apply modifications to the JS7_CONFIG_DIR/private/private.conf file In order to apply modifications to ./config/private/private.conf files of the Controller or to configuration files of JOC Cockpit a restart of the respective component is required..

Space shortcuts

Page tree

Versions Compared

Old Version 5

New Version 6

Key

Secure Connection Setup

Step 1: Create the Keystore

Secure Connections for JOC Cockpit to Controller

Step 1: Create the Controller Keystore

Step 2: Set up Authentication to Controller

Step 3: Set up the Controller Instance Start Script for HTTPS

Step 4: Configure the JOC Cockpit Truststore

Step 2: Set up Authentication to Controller

Step 3: Set up the Controller for HTTPS

Step 4: Configure the JOC Cockpit Truststore

Mutual Authentication for JOC Cockpit to Controller

Step 1: Create Controller Trusstore

Notes

Notes

Further Resources

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 5

New Version 6

Key

Secure Connection Setup

Step 1: Create the Keystore

Secure Connections for JOC Cockpit to Controller

Step 1: Create the Controller Keystore

Step 2: Set up Authentication to Controller

Step 3: Set up the Controller Instance Start Script for HTTPS

Step 4: Configure the JOC Cockpit Truststore

Step 2: Set up Authentication to Controller

Step 3: Set up the Controller for HTTPS

Step 4: Configure the JOC Cockpit Truststore

Mutual Authentication for JOC Cockpit to Controller

Step 1: Create Controller Trusstore

Notes

Notes

Further Resources