JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 14

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Introduction

  • Connections from the JOC Cockpit to the Controller Controllers use the JS7 - REST Web Service API and can be secured by HTTPS with TLS/SSL certificates.

    • Should If the JOC Cockpit and Controller be are operated on the same server and network interface then no HTTPS connection between components products is required.

    • Should If the JOC Cockpit and Controller be 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.
    • Consider See the JS7 - System Architecture article for an overview of components products and connections.
    • Consider to set up Follow the instructions in the JS7 - JOC Cockpit HTTPS Connections for article to set up secure connections from clients (user browser / REST API client) to the JOC Cockpit.
    • Consider See the JS7 - Agent HTTPS Connections for article for information about securing the connections between Controller instances and Agents.

Prerequisites

  • 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. 

Certificate Management

Private keys and certificates should be distributed as follows:

  • The following explanations assume Private CA-signed Certificates or Public CA-signed Certificates to be used.
    • Private CA-signed Certificates are created by users who operate their own CA, see the JS7 - How to create X.509 SSL TLS Certificates.
    • Public CA-signed Certificates are provided from known and trusted Certificate Authorities (CA) that validate the domain owner.
    • Use of Intermediate CA Certificates is optional.
    • There is no difference in using a Private CA or Public CA concerning functionality of X.509 certificates, usage for Server Authentication / Client Authentication, or security of connections. The only difference is that users trust the Private CA that they set up on their own.
  • 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.

Certificate Management

Private Keys and Certificates should be distributed as follows:


Flowchart
Controller [label="   Controller   \nStandalone / Cluster",fillcolor="lightskyblue"]
JOC [label="   JOC Cockpit   \nPrimary",fillcolor="lightskyblue"]
JOC2 [label="   JOC Cockpit   \nSecondary",fillcolor="lightskyblue"]
 
Controller_Truststore [label="Controller Truststore\nhttps-truststore.p12\n\nCA certificates",fillcolor="limegreen"]
Controller_Keystore [label="Controller Keystore\nhttps-keystore.p12\n\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\nPrivate Key / Certificate",fillcolor="limegreen"]

Controller_Truststore_CA_RootCertificate
Flowchart
Controller [label="   Controller   \nStandalone / Primary",fillcolor="lightskyblue"]
JOC [label="   JOC Cockpit   \nPrimary",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",shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
JOC_Truststore_CA_RootCertificate [shape="ellipse",shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
JOC_Keystore_CA_RootCertificate [shape="ellipse",shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
JOC_Keystore_CA_IntermediateCertificate [shape="ellipse",label="CA Intermediate\nCertificate",fillcolor="white"]

Controller_Keystore_CA_RootCertificate [shape="ellipse",shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
Controller_Keystore_CA_IntermediateCertificate [shape="ellipse",label="CA Intermediate\nCertificate",fillcolor="white"]
Controller_PrivateKey [shape="ellipse",label="ServerCA AuthenticationRoot\nPrivate KeynCertificate",fillcolor="white"]
ControllerJOC_Truststore_KeystoreCA_CertificateRootCertificate [shape="ellipse",label="ServerCA AuthenticationRoot\nCertificate",fillcolor="white"]

JOC_PrivateKey#JOC_Keystore_CA_RootCertificate [shape="ellipse",label="ClientCA AuthenticationRoot\nPrivate KeynCertificate",fillcolor="white"]
JOC_Certificate#JOC_Keystore_CA_IntermediateCertificate [shape="ellipse",label="ClientCA AuthenticationIntermediate\nCertificate",fillcolor="white"]

Controller -> Controller#Controller_Keystore 
Controller_Keystore -> Controller_Keystore_CA_RootCertificate -> Controller_CA_RootCertificate [shape="ellipse",label="CA Root\nCertificate",fillcolor="white"]
#Controller_Keystore_CA_IntermediateCertificate [shape="ellipse",label=" add to keystore CA Intermediate\nCertificate",fillcolor="white"]
Controller_Keystore -> Controller_PrivateKey -> Controller_Keystore_Certificate [[shape="ellipse",label=" add to keystore "]

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

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

JOC -> JOC_Truststore
JOC_Truststore -> JOC_Truststore_CA_RootCertificateServer 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_Keystore -> Controller_Keystore_CA_RootCertificate -> Controller_Keystore_CA_IntermediateCertificate [label=" add to truststorekeystore "] 

JOC -> Controller

Explanation:

  • 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

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:
  • JETTY_HOME = JOC_HOME/jetty
  • JETTY_BASE is Jetty's base directory that is specified during JOC Cockpit installation:

For Controller instances the following placeholders are used:

  • JS7_CONTROLLER_HOME points to the Controller instance's installation directory
  • 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 from 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.

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

Controller_Keystore -> Controller_PrivateKey -> Controller_Keystore_Certificate [label=" add to keystore "]

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

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

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

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


Explanation:

  • 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.
    • The Root CA Certificate is added to the Controller's truststore.
  • 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.

Secure Connection Setup

In the following, the placeholders JOC_HOME, JETTY_HOME and JETTY_BASE are used to describe the location of three directories. If you install Jetty with the JOC Cockpit installer then:

  • 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)

The following placeholders are used for Controller instances:

Secure Connections from JOC Cockpit to Controller

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

Secure connections require authentication.

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

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 3rd-party utility.
    • For use with a 3rd-party utility create a keystore, e.g. https-keystore.p12, in PKCS12 format and import:
      • Controller Private Key and Certificate for Server Authentication
    • 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 a possible approach for certificate management - however, there are other ways of achieving similar results.

      • Example for importing a Private Key and CA-signed Certificate to a PKCS12 keystore:

        Code Block
        languagebash
        titleExample how to import a Private Key and CA-signed Certificate to a PKCS12 keystore
        # Assume the fully qualified domain name
    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
        languagebash
        titleExample 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 to beingbe "controller.example.com"
openssl pkcs12 -export -in controller-https.crt -inkey controller-https.key -chain -CAfile ca-bundle.crt -name

# 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 -out JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12.crt

# shouldImport youthe requireController's usePrivate 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
        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 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 CA-signed Certificate and import to a keystore

        generate a self-signed certificate for import into a PKCS12 Keystore
        • create a Private Key and CA-signed Certificate
          #
        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 "
        • Creating the Private Key and CA-signed Certificate for the given validity period
./create_server_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
          titleExample how to add a Private Key and CA-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
        .pk12" -storepass jobscheduler -storetype PKCS12

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

        Code Block
        languagebash
        titleExample 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) # 
        • .p12 \
    --key=controller.example.com.key \
    --cert=controller.example.com.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
          titleExample how to add a Private Key and CA-signed Certificate to a PKCS12 keystore and the Root CA Certificate to a truststore
          # Adding the Private Key and Certificate to a keystore and Root CA Certificate to a truststore
./js7_create_certificate_store.sh \
    --keystore=
        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 
          p12 \
    --truststore=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 
        • /private/https-truststore.p12 \ 
    --key=controller.example.com.key \
    --cert=controller.example.com.crt \
    --alias=controller.example.com \
    --password="jobscheduler" \
    --ca-root=root-ca.crt
    • With the keystore being set up, specify the relevant properties with 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.
      • DIR/private/private.conf configuration file:

      • Example

        Code Block
        languagetext
        titleExample 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"
      With the keystore being set up specify respective properties with the JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file:

      • Example

        Code Block
        languagetext
        titleExample for private.conf file specifying the Controller keystore
        js7 {
    web {
        #  keystore location for https connections
 key-password="jobscheduler"
         https {
      store-password="jobscheduler"
      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.

...

      • }
}


        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 3rd-party utility.
    • For use with a 3rd-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
        languagebash
        titleExample 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 is checked and a password is used to identify the JOC Cockpit instance.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 Consider that any number of clustered JOC Cockpit instances can connect to a Controller.
    • If a Controller cluster Cluster is used then connections from the partnering Controller instance are authenticated by the Distinguished Name of the instance's Client Authentication distinguished namecertificate.

  • The JS7_CONTROLLER_CONFIG_DIR/private/private.conf configuration file is should include authentication details like thissuch as:

    Code Block
    titleExample for private.conf file specifying JOC Cockpit authentication
    js7 {
    auth {
        users {
            # History account (used forto release events)
            History {
                distinguished-names=[
                    "DNQ=SOS CA, CN=apmacwinjoc_jocprimary_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=apmacwinjoc_jocprimary_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
 Controller instance
            jobscheduler {
                distinguished-names=[
  jobscheduler {
                distinguished-names=[
  "DNQ=SOS CA, CN=controller_primary_client, OU=IT, O=SOS, L=Berlin, ST=Berlin, C=DE",
                     "DNQ=SOS CA, CN=apmacwincontroller_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 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
languagexml
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

...

  • 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 truststore.

  • On the JOC Cockpit server create the truststore using the keytool from your Java JRE or JDK or some 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 JKS or PKCS12 format with the Root CA certificate. The below examples suggest one possible approach for certificate management, however, there may be other ways how to achieve similar results.

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

        Code Block
        languagebash
        titleExample 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
        languagebash
        titleExample 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
        languagebash
        titleExample 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 truststore

      Code Block
      languagetext
      ### 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 = ../../resources/joc/https-truststore.p12 
truststore_type = PKCS12
truststore_password = jobscheduler

    • Example for JKS truststore

      Code Block
      languagetext
      ### 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 = ../../resources/joc/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
    ################################################################################
### Should hostname verification be carried out for https certificate. 
### Default false

https_with_hostname_verification = true

Mutual Authentication for Controller

This configuration is applied in order to enable mutual authentication

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

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 use of 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 keystore as indicated with the JS7 - JOC Cockpit HTTPS Connections article.
  • If separate private key/certificate pairs should be used for Server Authentication and Client Authentication purposes then use of separate certificate stores for JOC Cockpit is recommended:
    • The keystore holds the private key/certificate for Server Authentication.
    • The client keystore holds the private key/certificate for Client Authentication.

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

  • On the JOC Cockpit server create the client keystore using the keytool from your Java JRE or JDK or some 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:
      • JOC Cockpit private key and certificate for Client Authentication
      • Root CA certificate
      • Intermediate CA certificates
    • 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 indicated steps 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 PKCS12 client keystore:

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

client_keystore_path = ../../resources/joc/https-truststore.p12 
client_keystore_type = PKCS12
client_keystore_password = jobscheduler

    • Example for JKS client keystore:

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

client_keystore_path = ../../resources/joc/https-truststore.jks
client_keystore_type = JKS
client_keystore_password = jobscheduler

Step 2: Create Controller Truststore

...

  • Root CA certificate

...

      • allows the addition of a number of Distinguished Names as available from the 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.
        • 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
      languagexml
      titleExample 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
      languagexml
      titleExample for HTTP and HTTPS port settings with Controller Instance Start Script for Windows
      collapsetrue
      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 3rd-party utility.
    • For use with a 3rd-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
        languagebash
        titleExample 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
      languagetext
      titleExample 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
      languagetext
      titleExample how to specify a JKS truststore location with the joc.properties file
      collapsetrue
      ### 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.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
    titleExample 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 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 3rd-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
      languagetext
      titleExample 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
      languagetext
      titleExample how to specify the JKS client keystore location with 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
Show If
matchall
userap

Risk Mitigation

The descriptions above indicate use of a Root CA Certificate

...

Code Block
languagebash
titleExample how to import a CA signed certificate into a PKCS12 Truststore
# on JOC Cockpit server: 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" -storetype PKCS12

...

Example for export/import of self-signed certificate to a PKCS12 keystore:

Code Block
languagebash
titleExample how to export the Master public certificate from a PKCS12 Keystore
# on Controller server: export Controller's certificate from keystore (https-keystore.p12) identified by its alias name (controller-https) to a file in PEM format (controller-https.crt)
keytool -exportcert -rfc -noprompt -file "controller-https.crt" -alias "controller-https" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.p12" -storepass jobscheduler -storetype PKCS12

# on JOC Cockpit server: import Controller certificate in PEM format to a PKCS12 truststore (https-truststore.p12)
keytool -import -alias "controller-https" -file "controller-https.crt" -keystore "JETTY_BASE/resources/joc/https-truststore.p12" -storetype PKCS12

...

Example for export/import of self-signed certificate to a JKS keystore:

Code Block
languagebash
titleExample how to export the Master public certificate from a JKS Keystore
# on Controller server: export Controller's certificate from keystore (https-keystore.jks) identified by its alias name (controller-https) to a file in PEM format (controller-https.crt)
keytool -exportcert -rfc -noprompt -file "controller-https.crt" -alias "controller-https" -keystore "JS7_CONTROLLER_CONFIG_DIR/private/https-keystore.jks" -storepass jobscheduler

# on JOC Cockpit server: import Controller certificate in PEM format to a JKS truststore (https-truststore.jks)
keytool -import -alias "controller-https" -file "controller-https.crt" -keystore "JETTY_BASE/resources/joc/https-truststore.jks" -storetype JKS

Risk Mitigation

...

for verification of Client Authentication certificates when it comes to mutual authentication.

  • In fact use of a Root CA

...

  • Certificate allows any clients

...

  • with a Client Authentication certificate signed by the same Root CA

...

  • 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

    ...

      • Certificate.

    Notes

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

    ...

    Resources