Connections from the JOC Cockpit to Controllers use the JS7 - REST Web Service API and can be secured by HTTPS with TLS/SSL certificates.
- If the JOC Cockpit and Controller are operated on the same server and network interface then no HTTPS connection between components products is required.
- If the JOC Cockpit and Controller are operated on different servers or network interfaces then this connection should be secured by HTTPS.
This article describes the steps required to set up secure HTTPS communication from the JOC Cockpit to a Controller. This includes to use a standalone Controller or a Controller cluster Cluster with an active instance and a primary and standby instance.
- See the JS7 - System Architecture article for an overview of components products and connections.
- Follow the instructions in the JS7 - JOC Cockpit HTTPS Connections article to set up secure connections from clients (user browser / REST API client) to the JOC Cockpit.
- See the JS7 - Agent HTTPS Connections article for information about securing the connections between Controller instances and Agents.

Prerequisites

The following explanations assume CA-signed certificates or self-signed certificates to be used.
- CA-signed certificates are provided from known and trusted Certificate Authorities (CA) that validate the domain owner.
- Self-signed certificates are created by users who operate their own CA, see the JS7 - How to create self-signed Certificates.
- Use of Intermediate CA Certificates is optional.
Certificate stores can be managed from the command line and by use of tools that provide a GUI for this purpose:
- the Java keytool is available from the Java JRE or JDK,
- the Keystore Explorer is an open source utility to graphically manage certificate stores.
Starting from Java 9 the PKCS12 keystore type is default and is not required to be specified with keytool.
The following sections assume a PKCS12 keystore/truststore format. For Unix OS the .p12 file extension frequently is used, for Windows OS the .pfx extension is preferably used. Both file extensions indicate the same PKCS12 format and can be used interchangeably.

...

Flowchart

Controller [label="&nbsp;&nbsp;&nbsp;Controller&nbsp;&nbsp;&nbsp;\nStandalone / Cluster",fillcolor="lightskyblue"]
JOC [label="&nbsp;&nbsp;&nbsp;JOC Cockpit&nbsp;&nbsp;&nbsp;\nPrimary",fillcolor="lightskyblue"]
JOC2 [label="&nbsp;&nbsp;&nbsp;JOC Cockpit&nbsp;&nbsp;&nbsp;\nStandbynSecondary",fillcolor="lightskyblue"]
 
Controller_Truststore [label="Controller Truststore\nhttps-truststore.p12\n\nCA certificates",fillcolor="limegreen"]
Controller_Keystore [label="Controller Keystore\nhttps-keystore.p12\n\nCA Certificates\nPrivate Key / Certificate",fillcolor="orange"]
JOC_Truststore [label="JOC Cockpit Truststore\nhttps-truststore.p12\n\nCA certificates",fillcolor="orange"]
JOC_Keystore [label="JOC Cockpit Keystore\nhttps-keystore.p12\n\nCA Certificates\nPrivate Key / Certificate",fillcolor="limegreen"]

Controller_Truststore_CA_RootCertificate [shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
JOC_Truststore_CA_RootCertificate [shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
JOC#JOC_Keystore_CA_RootCertificate [shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
JOC#JOC_Keystore_CA_IntermediateCertificate [shape="ellipse",label="CA Intermediate\nCertificate",fillcolor="white"]

Controller#Controller_Keystore_CA_RootCertificate [shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
Controller#Controller_Keystore_CA_IntermediateCertificate [shape="ellipse",label="CA Intermediate\nCertificate",fillcolor="white"]
Controller_PrivateKey [shape="ellipse",label="Server Authentication\nPrivate Key",fillcolor="white"]
Controller_Keystore_Certificate [shape="ellipse",label="Server Authentication\nCertificate",fillcolor="white"]

JOC_PrivateKey [shape="ellipse",label="Client Authentication\nPrivate Key",fillcolor="white"]
JOC_Certificate [shape="ellipse",label="Client Authentication\nCertificate",fillcolor="white"]

Controller -> Controller_Keystore 
Controller#Controller_Keystore -> Controller_Keystore_CA_RootCertificate -> Controller_Keystore_CA_IntermediateCertificate [label="&nbsp;add to keystore&nbsp;"]
Controller_Keystore -> Controller_PrivateKey -> Controller_Keystore_Certificate [label="&nbsp;add to keystore&nbsp;"]

Controller -> Controller_Truststore 
Controller_Truststore -> Controller_Truststore_CA_RootCertificate [label="&nbsp;add to truststore&nbsp;"]

JOC -> JOC_Keystore 
JOC#JOC_Keystore -> JOC_Keystore_CA_RootCertificate -> JOC_Keystore_CA_IntermediateCertificate [label="&nbsp;add to keystore&nbsp;"]
JOC_Keystore -> JOC_PrivateKey -> JOC_Certificate [label="&nbsp;add to keystore&nbsp;"]

JOC -> JOC_Truststore
JOC_Truststore -> JOC_Truststore_CA_RootCertificate [label="&nbsp;add to truststore&nbsp;"] 

JOC -> Controller [label="&nbsp;establish connection&nbsp;"]
JOC2 -> Controller [label="&nbsp;establish connection&nbsp;"]

...

Keystore and truststore shown in orange 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. If the certificate is self-signed, then it has to be added to the JOC Cockpit's truststore as well.
- The Root CA Certificate is added to the Controller's truststoreThis step can be skipped if a CA-signed certificate is used as the Root Certificate in the JOC Cockpit's truststore is sufficient to verify Controller certificates.
The keystore and truststore shown in green are required if mutual authentication is in place for certificate based client authentication (default).
The Controller's truststore shown in green is required should secure connections be used by a Controller to access Agents. It is therefore recommended the Controller's truststore is set up.
Similar certificate management applies for any additional standby JOC Cockpit instances acting in a cluster.

...

JOC_HOME is the installation path that is specified during the JOC Cockpit installation:
- /opt/sos-berlin.com/js7/joc (default on Unix)
- 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 the JOC Cockpit installation:
- /home/<setup-user>/sos-berlin.com/js7/joc (default on Unix)
- C:\ProgramData\sos-berlin.com\js7\joc (default on Windows)

...

JS7_CONTROLLER_HOME points to the Controller instance's installation directory
- /opt/sos-berlin.com/js7/controller <extraction-directory>/controller (default on Unix)/Windows for JS7 - Controller - Headless Installation on Linux and Windows)
- C:\Program Files\sos-berlin.com\js7\controller (default on Windows for JS7 - Controller - Installation Using the Windows Graphical Installer)
JS7_CONTROLLER_CONFIG_DIR points to is the Controller instance's configuration directory that is specified during installation:
- <extraction-directory/controller/var
- /var/sos-berlin.com/js7/controller/config (default on Unix/Windows for JS7 - Controller - Headless Installation on Linux and Windows)
- C:\ProgramData\sos-berlin.com\js7\controller\config (default on Windows for JS7 - Controller - Installation Using the Windows Graphical Installer)

Secure Connections from JOC Cockpit to Controller

...

The following sections assume mutual authentication to be in place.

Anchor
server_authentication_create_keystore
server_authentication_create_keystore
Step 1:

...

Creating the Controller Keystore and Truststore

On the Controller instance's server create the keystore using openssl and the keytool from your Java JRE or JDK or a 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 AuthenticationRoot CA certificate
- Intermediate CA certificate(s)

For use with openssl and keytool create the keystore with the private key and certificate for Server Authentication from the command line. The examples below show one a possible approach for certificate management - however, there are other ways of achieving similar results.

Example for creating importing a private key and CA-signed certificate with to a PKCS12 keystore:

Code Block

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

# IfAssume the Controller'sfully privatequalified keydomain andname certificate(FQDN) areof tothe beController providedserver withto abe .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's private key to be "controller.example.com"
# keytool -importkeystore -srckeystore keypair.jks -srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12 -srcalias"controller.example.com"

# If the Controller's CA-signed certificate is provided from a pkcs12 keystore (certificate.p12), extract the certificate to a .crt file in PEM format (controller.example.com.crt)
# openssl pkcs12 -in certificate.p12 -nokeys -out controller.example.com.crt

# assumingImport the Controller's private key from a pkcs12 keystore (keystore.p12), store the Controller's private key in a .key file in PEM format (controller-https.key(controller.example.com.key) and certificate (controller.example.com.crt) from PEM format to a new keystore (https-keystore.p12)
openssl pkcs12 -export -in keystore.p12 -nocerts -out controller-https.key

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

# Export the 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)
#   assuming the fully qualified domain name (FQDN) of the Controller server is "controller.example.com"
openssl pkcs12 -export -in controller-https.crt -inkey controller-https.key -chain -CAfile ca-bundle.crt -name controller.example.com -out controller.example.com.crt -inkey controller.example.com.key -name controller.example.com -out "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12"

Example for creating a private key and self-signed certificate and import to a keystore

Refer to examples available from JS7 - How to create self-signed Certificates, chapter Creating a Server Certificate.

Code Block

language	bash
title	Example how to create a private key and self-signed certificate

# Creating the private key and self-signed certificate for the given validity period
./create_certificate.sh --dns=controller.example.com --days=365

Refer to examples available from JS7 - How to add SSL TLS Certificates to Keystore and Truststore.

Code Block

title	Example how to add a private key and self-signed certificate to a PKCS12 keystore

# Adding the private key and certificate to a keystore
./js7_create_certificate_store.sh \
    --keystore=JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12

\

#

IF

you

require use of a .jks keystore type then convert the pkcs12 keystore, assuming the alias name of the Controller private key being " Code Blocklanguagebash

 --key=controller.example.com.key \
    --cert=controller.example.com

" # keytool -importkeystore -srckeystore https-keystore.p12 -srcstoretype PKCS12 -destkeystore JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.jks -deststoretype JKS -srcalias controller.example.com

Example for creating private key and self-signed certificate with PKCS12 keystore:

.crt \ --alias=controller.example.com \ --password="jobscheduler"
When using additional arguments for creation of a truststore then users have the truststore available for the later step 4:
Code Block

title Example how to

generate

add a private key and self-signed certificate

for import into

to a PKCS12 keystore

collapsetrue

and the Root CA Certificate to a truststore
#

generate

Adding the

Controller's

private key

with

and

alias

certificate

name "controller.example.com" in

to a keystore

(https-keystore.p12) # use the fully qualified domain name (FQDN) assumed to be "

and Root CA Certificate to a truststore
./js7_create_certificate_store.sh \
    --keystore=JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12 \
    --truststore=JS7_CONTROLLER_CONFIG_DIR/private/https-truststore.p12 \ 
    --key=controller.example.com

"

.key

and

\

name

of

your organization for the distinguished name # consider that PKCS12 keystores require the use of the same key password and store password keytool -genkey -alias "

 --cert=controller.example.com.crt \
    --alias=controller.example.com

"

\ -

dname "CN=controller.example.com,O=organization" -validity 1461 -keyalg RSA -keysize 2048 -keypass jobscheduler -keystore "

-password="jobscheduler" \
    --ca-root=root-ca.crt

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

Example

https-keystore.p12" -storepass jobscheduler -storetype PKCS12

Example for creating a private key and self-signed certificate with JKS keystore:

Code Block

language	bashtext
title	Example how to generate a private key and self-signed certificate for import into a JKS keystore
collapse	true
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}"# generate the Controller's private key with the alias name "controller.example.com" in a keystore (https-keystore.jks)
#   use the fully qualified domain name (FQDN) assumed to be "controller.example.com" and name of your organization for the distinguished name
keytool -genkey -alias "controller.example.com" -dname "CN=controller.example.com,O=organization" -validity 1461 -keyalg RSA -keysize 2048 -keypass jobscheduler -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.jksp12"
 -storepass  jobscheduler -storetype JKS

Explanation:
- 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.
- The -keystore option specifies the location of the keystore file. The keystore file should be in reach of the Controller, it is recommended using the private sub-folder in the JS7_CONTROLLER_CONFIG_DIR directory.
- The -storepass option specifies the password for access to the keystore file.
- The -storetype option is used to specify the PKCS12 or JKS keystore format.

With the keystore set up, specify the relevant 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 for Controller

- - 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. Passwords for private key and keystore have to match when using PKCS12 keystores.

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

For use with a third party utility create a truststore, e.g. https-truststore.p12, in PKCS12 format and import:
- Root CA Certificate

The examples below show a possible approach for certificate management - however, there are other ways of achieving similar results.

Example for importing a Root CA Certificate to a PKCS12 truststore:

Code Block

language	bash
title	Example how to import a Root CA Certificate to a PKCS12 truststore

# Import Root CA Certificate in PEM format to a PKCS12 truststore (https-truststore.p12)
keytool -importcert -alias "root-ca" -file "root-ca.crt" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-truststore.p12" -storetype PKCS12

Step 2: Setting up Authentication with the Controller

By default mutual authentication is in place.
- JOC Cockpit makes use of two connections to the Controller: one for the JS7 - History Service and one for the JOC Cockpit GUI. Both connections by default use mutual authentication.
- The JOC Cockpit is challenged by the Controller to present its Client Authentication certificate that is then verified by the Controller.
  - In addition the Distinguished Name of the JOC Cockpit Client Authentication certificate is checked. An additional password setting has to be present but can be empty as in password="plain:". JOC Cockpit ships with the below default passwords. If a password is changed in the Controller configuration then it has to be changed in the JS7 - Settings too.
  - Note 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 the Distinguished Name of the instance's Client Authentication certificate.
The JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file should include authentication details such as:
Code Block
title Example for private.conf file specifying JOC Cockpit authentication
js7 { auth { users { # History account (used to release events) History
By default mutual authentication is in place.
- The JOC Cockpit is challenged by the Controller to present its Client Authentication certificate that is then verified by the Controller.
  - In addition the Distinguished Name of the JOC Cockpit Client Authentication certificate is checked and a password is used to identify the JOC Cockpit instance.
  - Note 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 the Distinguished Name of the instance's Client Authentication certificate.

The JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file should include authentication details such as:

Code Block

title	Example for private.conf file specifying JOC Cockpit authentication

js7 {
    auth {
        users {
            # History account (used for releasing events)
            History {
                distinguished-distinguished-names=[
                    "DNQ=SOS CA, CN=joc_primary_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=joc_primary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
                password="sha512:3662FD6BF84C6B8385FC15F66A137AB75C755147A81CC7AE64092BFE8A18723A7C049D459AB35C059B78FD6028BB61DCFC55801AE3894D2B52401643F17A07FE"
                permissions=[
                    UpdateItem
                ]
            }
            # Controller ID for connections by primary/secondary controllerController instance
            jobscheduler {
                distinguished-names=[
                     "DNQ=SOS CA, CN=controller_primary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE",
                     "DNQ=SOS CA, CN=controller_secondary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE"
                ]
                password="plain:"
           }
        }
     }
}

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 allows the addition of a number of Distinguished Names as available from the subject subjects of the Client Authentication certificates which are used by JOC Cockpit instances when connecting to the Controller.
  - Except for whitespace between attributes, the precise sequence and values as available from the certificate's subject has to match this property value.
  The password is used for authentication of the History and JOC service accounts with the Controller. Both accounts are typically running in the same JOC Cockpit instance.
- If HTTP connections are used then the password is the only means for authentication. If HTTPS connections with mutual authentication are used then the password is not relevant as certificate based authentication is in place.
- In the private.conf file a hashed value or a plain text value can be specified like this:
  - password="sha512:B793649879D6..."
  - password="plain:JS7-History"
- If the password is modified in the private.conf file then it has to be modified in the JOC Cockpit settings as well, so that the passwords match.
- The password setting cannot be omitted. However, an empty password can be specified, for example, with mutual authentication HTTPS connections such as:
  - password="plain:"
- From the private.conf file that ships by default the plain text value and the hashed values are:
  - History:
    - Plain Text: JS7-History
    - Hash: sha512:B793649879D61613FD3F711B68F7FF3DB19F2FE2D2C136E8523ABC87612219D5AECB4A09035AD88D544E227400A0A56F02BC990CF0D4CB348F8413DE00BCBF08
  - JOC:
    - Plain Text: JS7-JOC
    - Hash: sha512:3662FD6BF84C6B8385FC15F66A137AB75C755147A81CC7AE64092BFE8A18723A7C049D459AB35C059B78FD6028BB61DCFC55801AE3894D2B52401643F17A07FE
The jobscheduler user account is an example of a Controller ID that is 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 Instance Start Script.

...

For Unix the Instance Start Script is available from JS7_CONTROLLER_HOME/bin/controller_instance.sh:

Code Block

language	xml
title	Example for HTTP and HTTPS port settings with Controller Instance Start Script for Unix

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

JS7_CONTROLLER_HTTP_PORT=localhost:4444


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

JS7_CONTROLLER_HTTPS_PORT=controller.example.com:4444

For Windows the Instance Start Script is available from JS7_CONTROLLER_HOME\bin\controller_instance.cmd:

- - - If more than one Distinguished Name is used then they are separated by comma.
    - Distinguished Names can be displayed in different flavors. JS7 makes use of RFC2253 compliant Distinguished Names. The following command can be executed to verify the Distinguished Name from a given certificate file:
      - openssl x509 -in <joc-cert.pem> -noout -nameopt RFC2253 -subject
      - The output that you receive - except for a subject: or subject= prefix - should be used as the JOC Cockpit's Distinguished Name
      - Sample Output:
        subject= ST=Berlin,OU=JS7,O=SOS,L=Berlin,C=DE,CN=centostest-primary
        The prefix subject= has to be omitted from the Distinguished Name.
  - The password is used for authentication of the History and JOC service accounts with the Controller. Both accounts are typically run in the same JOC Cockpit instance.
    - If HTTP connections are used then the password is the only means for authentication. If HTTPS connections with mutual authentication are used then the password is not relevant as certificate based authentication is in place.
    - The symmetric password is specified in the joc section of the JS7 - Settingspage of the JOC Cockpit and in the private.conf file.
      User Input to the Settings page of the JOC Cockpit can look like this:
      
      Image Added
      
      Input to the GUI simply accepts the password and does not require the use of the sha512: or plain: prefixes.
    - In the private.conf file a hashed value or a plain text value can be specified like this:
      password="sha512:B793649879D6..."
      password="plain:JS7-History"
    - If the password is modified in the private.conf file then it has to be modified in the JOC Cockpit settings as well, so that the passwords match.
    - The password setting cannot be omitted. However, an empty password can be specified, for example:
      password="plain:"
    - From the private.conf file that ships by default the plain text value and the hashed values are:
      History:
      Plain Text: JS7-History
      Hash: sha512:B793649879D61613FD3F711B68F7FF3DB19F2FE2D2C136E8523ABC87612219D5AECB4A09035AD88D544E227400A0A56F02BC990CF0D4CB348F8413DE00BCBF08
      JOC:
      Plain Text: JS7-JOC
      Hash: sha512:3662FD6BF84C6B8385FC15F66A137AB75C755147A81CC7AE64092BFE8A18723A7C049D459AB35C059B78FD6028BB61DCFC55801AE3894D2B52401643F17A07FE
- The jobscheduler account is an example of the Controller ID that is 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: Setting 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 Instance Start Script.

For Unix the Instance Start Script is available from JS7_CONTROLLER_HOME/bin/controller_instance.sh:

Code Block

language	xml
title	Example for HTTP and HTTPS port settings with Controller Instance Start Script for Unix

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

JS7_CONTROLLER_HTTP_PORT=localhost:4444


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

JS7_CONTROLLER_HTTPS_PORT=controller.example.com:4444

For Windows the Instance Start Script is available from JS7_CONTROLLER_HOME\bin\controller_instance.cmd:

Code Block

language	xml
title	Example for HTTP and HTTPS port settings with Controller Instance Start Script for Windows
collapse	true

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=controller.example.com:4444

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

Step 4: Configuring the JOC Cockpit Truststore

The Root CA Certificate is added to the JOC Cockpit truststore. This step can be skipped if the JOC Cockpit truststore is available, see JS7 - JOC Cockpit HTTPS Connections.

On the JOC Cockpit server create the truststore using the keytool from your Java JRE or JDK or a third party utility.
For use with a third party utility create a truststore, e.g. https-truststore.p12, in PKCS12 format and import:
Root CA Certificate
For use with keytool create the truststore in PKCS12 or JKS format with the Root CA Certificate. The examples below show a possible approach for certificate management - however, there are other ways how to achieve similar results.
Example showing how to import a Root CA Certificate to a PKCS12 truststore:
Code Block
language bash
title Example how to import a Root CA Certificate into a PKCS12 truststore
# import Root CA Certificate in PEM format to a PKCS12 truststore (https-truststore.p12) keytool -importcert -alias "root-ca" -file "root-ca.crt" -keystore "JETTY_BASE/resources/joc/https-truststore.p12" -storetype PKCS12

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

Example for a PKCS12 truststore

Code Block

language	text
title	Example how to specify a PKCS12 truststore location with the joc.properties file

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

truststore_path = https-truststore.p12 
truststore_type = PKCS12
truststore_password = jobscheduler

Example for a JKS truststore

Code Block

language	xml
title	Example for HTTP and HTTPS port settings with Controller Instance Start Script for Windows
collapse	true

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=controller.example.com:4444

...

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

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's truststore.

On the JOC Cockpit server create the truststore using the keytool from your Java JRE or JDK or a third party utility.
For use with a third party utility create a truststore, e.g. https-truststore.p12, in PKCS12 format and import:
Root CA certificate
For use with keytool create the truststore in PKCS12 or JKS format with the Root CA certificate. The examples below show one possible approach for certificate management - however, there are other ways how to achieve similar results.
Example showing the import 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 -importcert -alias "root-ca" -file "RootCACertificate.crt" -keystore "JETTY_BASE/resources/joc/https-truststore.p12" -storetype PKCS12
Example showing the use of a self-signed Controller certificate with a PKCS12 truststore:
Code Block
language bash
title Example for import of a self-signed Controller certificate to a PKCS12 truststore
collapse true
# on the Controller server: export Controller's certificate from keystore (https-keystore.p12) identified by its alias name (controller.example.com) to a file in PEM format (controller-https.crt) keytool -exportcert -rfc -noprompt -file "controller-https.crt" -alias "controller.example.com" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12" -storepass jobscheduler -storetype PKCS12 # on the JOC Cockpit server: import the Controller's certificate from a file in PEM format (controller-https.crt) identified by its alias name (controller.example.com) to the JOC Cockpit PKCS12 truststore (https-truststore.p12) keytool -importcert -noprompt -file "controller-https.crt" -alias "controller.example.com" -keystore "JETTY_BASE/resources/joc/https-truststore.p12" -storepass jobscheduler -storetype PKCS12 -trustcacerts
Example showing the use of a self-signed Controller certificate with a JKS truststore:
Code Block
language bash
title Example for import of a self-signed Controller certificate to a JKS truststore
collapse true
# on the Controller server: export Controller's certificate from keystore (https-keystore.jks) identified by its alias name (controller.example.com) to a file in PEM format (controller-https.crt) keytool -exportcert -rfc -noprompt -file "controller-https.crt" -alias "controller.example.com" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.jks" -storepass jobscheduler -storetype JKS # on the JOC Cockpit server: import the Controller's certificate from a file in PEM format (controller-https.crt) identified by its alias name (controller.example.com) to the JOC Cockpit JKS truststore (https-truststore.jks) keytool -importcert -noprompt -file "controller-https.crt" -alias "controller.example.com" -keystore "JETTY_BASE/resources/joc/https-truststore.jks" -storepass jobscheduler -trustcacerts -storetype JKS

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

Example for a PKCS12 truststore

Code Block

language	text
title	Example how to specify a PKCS12 truststore location with the joc.properties file

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

truststore_path = https-truststore.p12 
truststore_type = PKCS12
truststore_password = jobscheduler

Example for a JKS truststore

Code Block

language	text
title	Example how to specify a JKS truststore location with the joc.properties file
collapse	true

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

truststore_path = https-truststore.jks
truststore_type = JKS
truststore_password = jobscheduler

Hostname verification by default is in place with the JETTY_BASE/resources/joc/joc.properties configuration file.

Code Block

title	Example how to specify hostname verification with the joc.properties file

################################################################################
### Specifies if hostname verification should be carried out for HTTPS connections.
### Default true

https_with_hostname_verification = true

Mutual Authentication for JOC Cockpit and Controller

This configuration is applied in order to enable mutual authentication:

from JOC Cockpit to the Controller:
the JOC Cockpit verifies the Controller's certificate for Server Authentication
the Controller verifies the JOC Cockpit's certificate for Client Authentication
from pairing Controller instances.

If mutual authentication cannot be used then consider explanations from the JS7 - Configuration for HTTPS Server Authentication with Passwords article.

Step 1: Create/Update JOC Cockpit Client Keystore

For mutual authentication JOC Cockpit has to hold a Client Authentication private key and certificate in its keystore.

This can be simplified by the use of a private key/certificate pair that is created for both extended key usages Server Authentication and Client Authentication. In this case a single private key and certificate is stored with the JOC Cockpit's keystore as described in the JS7 - JOC Cockpit HTTPS Connections article.
If separate private key/certificate pairs are be used for Server Authentication and Client Authentication purposes then use of separate certificate stores for the JOC Cockpit is recommended:
The keystore holds the private key/certificate for Server Authentication. The location of the keystore is configured with JETTY_BASE/start.ini.
The client keystore holds the private key/certificate for Client Authentication. The location of the client keystore is configured with JETTY_BASE/resources/joc/joc.properties.

The following steps are applied if a separate client keystore is used with the JOC Cockpit.

On the JOC Cockpit server create the client keystore using the keytool from your Java JRE or JDK or a third party utility.
For use with a third party utility create a client keystore, e.g. https-client-keystore.p12, in PKCS12 format and import:
the JOC Cockpit private key and certificate for Client Authentication
the Root CA certificate
Intermediate CA certificate(s)
For use with keytool create the client keystore in PKCS12 or JKS format according to the steps indicated with JS7 - JOC Cockpit HTTPS Connections: Step 2: Create JOC Cockpit Keystore chapter.
Apply the steps indicated to the client keystore and use the private key/certificate pair for Client Authentication.

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

Example for a PKCS12 client keystore:

Code Block

language	text
title	Example how to specify the PKCS12 client keystore a JKS truststore location with the joc.properties file
collapse	true

### Location of the client keystoretruststore that contains the privatecertificates keyof and all
###   certificate for JOC Cockpit client authentication relative to
###   Controllers used with HTTPS connections. The path can be absolute or 
###   relative to joc.properties

keystoretruststore_path = https-client-keystore.p12 
keystoretruststore.jks
truststore_type = PKCS12JKS
keystoretruststore_password = jobscheduler

Example for a JKS client keystore:

Hostname verification by default is in place with the JETTY_BASE/resources/joc/joc.properties configuration file.
Code Block
languagetext
title Example how to specify
the JKS client keystore location with
hostname verification with the joc.properties file
collapsetrue### Location of the client keystore that contains the private key and
################################################################################ ###
certificate for JOC Cockpit client authentication relative to ### joc.properties keystore_path = https-client-keystore.jks keystore_type = JKS keystore_password = jobscheduler

Step 2: Create Controller Truststore

Specifies if hostname verification should be carried out for HTTPS connections.
### Default true

https_with_hostname_verification = true

Mutual Authentication for JOC Cockpit and Controller

This configuration is applied in order to enable mutual authentication:

from JOC Cockpit to the Controller:
the JOC Cockpit verifies the Controller's certificate for Server Authentication
the Controller verifies the JOC Cockpit's certificate for Client Authentication
from pairing Controller instances.

If mutual authentication cannot be used then refer to explanations in the JS7 - Configuration for HTTPS Server Authentication with Passwords article.

Creating/Updating the JOC Cockpit Client Keystore

For mutual authentication JOC Cockpit has to hold a Client Authentication private key and certificate in its keystore.

This can be simplified by the use of a private key/certificate pair that is created for both extended key usages Server Authentication and Client Authentication. In this case a single private key and certificate is stored with the JOC Cockpit's keystore as described in the JS7 - JOC Cockpit HTTPS Connections article.
If separate private key/certificate pairs for Server Authentication and Client Authentication purposes are used then use of separate certificate stores for the JOC Cockpit is recommended:
The keystore holds the private key/certificate for Server Authentication. The location of the keystore is configured with JETTY_BASE/start.ini.
The client keystore holds the private key/certificate for Client Authentication. The location of the client keystore is configured with JETTY_BASE/resources/joc/joc.properties.

The following steps are applied if a separate client keystore is used with the JOC Cockpit.

On the JOC Cockpit server create the client keystore using the keytool from your Java JRE or JDK or a third party utility.
For use with a 3rd-party utility create a client keystore, e.g. https-client-keystore.p12, in PKCS12 format and import:
the JOC Cockpit private key and certificate for Client Authentication
For use with keytool create the client keystore in PKCS12 or JKS format according to the steps indicated with JS7 - JOC Cockpit HTTPS Connections: Step 2: Create JOC Cockpit Keystore chapter.
Apply the steps indicated to the client keystore and use the private key/certificate pair for Client Authentication.

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

Example for a PKCS12 client keystore:

Code Block

language	text
title	Example how to specify the PKCS12 client keystore location with joc.properties file

### Location of the client keystore that contains the private key and 
###   certificate for JOC Cockpit client authentication relative to
###   joc.properties

keystore_path = https-client-keystore.p12 
keystore_type = PKCS12
keystore_password = jobscheduler

Example for a JKS client keystore:

Code Block

language	text
title	Example how to specify the JKS client keystore location with joc.properties file
collapse	true

### Location of the client keystore that contains the private key and 
###   certificate for JOC Cockpit client authentication relative to
###   joc.properties

keystore_path = https-client-keystore.jks
keystore_type = JKS
keystore_password = jobscheduler

On the Controller server create the truststore using the keytool from your Java JRE or JDK or a third party utility.
For use with a third party utility create a truststore, e.g. https-truststore.p12, in PKCS12 format and import:
Root CA certificate
For use with keytool create the truststore in PKCS12 or JKS format with the Root CA certificate. The below examples suggest one possible approach for certificate management, however, there are other ways how to achieve similar results.
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
# on Controller server: import Root CA certificate in PEM format to a PKCS12 truststore (https-truststore.p12) keytool -importcert -alias "root-ca" -file "RootCACertificate.crt" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-truststore.p12" -storetype PKCS12
Example for export/import of self-signed Client Authentication certificate to a PKCS12 keystore:
Code Block
language bash
title Example how to export/import a self-signed certificate to a PKCS12 truststore
collapse true
# on JOC Cockpit server: export JOC Cockpit's certificate from client keystore (https-client-keystore.p12) identified by its alias name (joc-client-https) to a file in PEM format (joc-client-https.crt) keytool -exportcert -rfc -noprompt -file "joc-client-https.crt" -alias "joc-client-https" -keystore "JETTY_BASE/resources/joc/https-client-keystore.p12" -storepass jobscheduler -storetype PKCS12 # on Controller server: import JOC Cockpit's certificate in PEM format to a PKCS12 truststore (https-truststore.p12) keytool -importcert -alias "joc-client-https" -file "joc-clent-https.crt" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-truststore.p12" -storetype PKCS12
Example for export/import of self-signed Client Authentication certificate to a JKS keystore:
Code Block
language bash
title Example how to export/import a self-signed certificate to a JKS truststore
collapse true
# on JOC Cockpit server: export JOC Cockpit's certificate from client keystore (https-client-keystore.jks) identified by its alias name (joc-client-https) to a file in PEM format (joc-client-https.crt) keytool -exportcert -rfc -noprompt -file "joc-client-https.crt" -alias "joc-client-https" -keystore "JETTY_BASE/resources/joc/https-client-keystore.jks" -storepass jobscheduler # on Controller server: import JOC Cockpit's certificate in PEM format to a JKS truststore (https-truststore.jks) keytool -importcert -alias "joc-client-https" -file "joc-client-https.crt" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-truststore.jks" -storetype JKS

Show If

match	all
user	ap

Risk Mitigation

The descriptions above indicate use of a Root CA certificate Certificate for verification of Client Authentication certificates when it comes to mutual authentication.

In fact use of a Root CA certificate Certificate allows any clients that dispose of with a Client Authentication certificate signed by the same Root CA certificate or Intermediate CA to be authenticated. This implication might allow an unwanted number of clients to access a Controller. By design the only clients to access a Controller should be JOC Cockpit instances.
Coping strategies include:
- using a separate certificate authority to sign Client Authentication certificates for access to Controllers.
- importing individual Client Authentication certificates to the Controller's truststore instead of using a Root CA certificateCertificate.

Notes

A restart of the relevant component product is required to apply modifications to the either the the Controller JS7_CONFIG_DIR/private/private.conf file of the Controller or to JOC Cockpit configuration files of the JOC Cockpit .

Space shortcuts

Page tree

Versions Compared

Old Version 41

New Version Current

Key

Prerequisites

Secure Connections from JOC Cockpit to Controller

Anchor
server_authentication_create_keystore
server_authentication_create_keystore
Step 1:

Creating the Controller Keystore and Truststore

Step 2: Set up Authentication for Controller

Step 2: Setting up Authentication with the Controller

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

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

Step 4: Configuring the JOC Cockpit Truststore

Step 4: Configure the JOC Cockpit Truststore

Mutual Authentication for JOC Cockpit and Controller

Step 1: Create/Update JOC Cockpit Client Keystore

Step 2: Create Controller Truststore

Mutual Authentication for JOC Cockpit and Controller

Creating/Updating the JOC Cockpit Client Keystore

Risk Mitigation

Notes

Further Resources

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 41

New Version Current

Key

Prerequisites

Secure Connections from JOC Cockpit to Controller

Anchorserver_authentication_create_keystoreserver_authentication_create_keystoreStep 1:

Creating the Controller Keystore and Truststore

Step 2: Set up Authentication for Controller

Step 2: Setting up Authentication with the Controller

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

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

Step 4: Configuring the JOC Cockpit Truststore

Step 4: Configure the JOC Cockpit Truststore

Mutual Authentication for JOC Cockpit and Controller

Step 1: Create/Update JOC Cockpit Client Keystore

Step 2: Create Controller Truststore

Mutual Authentication for JOC Cockpit and Controller

Creating/Updating the JOC Cockpit Client Keystore

Risk Mitigation

Notes

Further Resources

Anchor
server_authentication_create_keystore
server_authentication_create_keystore
Step 1: