JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 33

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 34

changes.mady.by.user Alan Amos

Saved on

Key

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

Table of Contents

Introduction

  • Users benefit from the The JS7 - Certificate Authority included with the JOC Cockpit benefits users by allowing them to create and to rollout private keys and certificates.
  • The built-in Certificate Authority:
    • creates X.509 certificates for HTTPS Mutual Authentication
      • between JOC Cockpit and Controller instances,
      • between Primary and Secondary Controller instances,
      • between Controller instances and Agents.
    • is not used to create Server Authentication Certificates for access to JOC Cockpit. Access is performed by user browsers , and therefore it is preferable to use a Server Authentication Certificate that is which has been signed by a known Certificate Authority for which user browsers include the Root CA certificateand whose Root CA certificate is recognized by user's browsers.
  • Users benefit from the simplified rollout of private keys and certificates when using the built-in Certificate Authority.

JS7 provides a Certificate Rollout Client available with as part of the Controller and Agent instance's Start Scripts to create and to rollout . This client creates and rolls out private keys and certificates using the built-in Certificate Authority. Rollout of private keys and certificates created with an external Certificate Authority are not in scope of the Certificate Rollout Client. The functionality includesCertificate Rollout Client provides the following functions:

  • use of a security token to authenticate with the JOC Cockpit by use of a security token, see JS7 - Certificate Authority - Manage Certificates with JOC Cockpit, for more information.
  • requesting to request a private key and certificate to be created by the JOC Cockpit on-the-fly,
  • to update updating a Controller or Agent instance's configuration for use of the private key and certificate with HTTPS mutual authentication.

...

Rollout of certificates includes to perform performing the following steps:

  • JOC Cockpit
  • Controller/Agent Instance
    • Both components include the Certificate Rollout Client that which is available from the Controller/Agent Instance Start Script.
    • The Certificate Rollout Client connects to the JOC Cockpit. Authentication is performed by use of using the one-time security token generated with in the previous step.
    • The JOC Cockpit Certificate Authority is requested to create a private key and Server/Client Authentication Certificate for the specified host. Private The private key and certificate are created on-the-fly and are returned to the Certificate Rollout Client. In addition, the JOC Cockpit stores the certificate with in the JS7 - Database.
      The Certificate Rollout Client:
      • stores the private key in a keystore file,
      • stores the Server/Client Authentication Certificate in a truststore file,
      • updates the configuration in the ./config/private/private.conf file.

...

Standard Arguments

The following arguments are used independently from an HTTP connection or HTTPS of whether the connection to the JOC Cockpit is made with HTTP or HTTPS:

Expand
titleList of Standard Arguments
ArgumentRequiredDescriptionExample
--joc-uriYes

URI of the JOC Cockpit instance from which to receive the private key and certificate.

--joc-uri=http://myhost.example.com:4446
--tokenYes

UUID of the security token for one-time authentication with the JOC Cockpit.

--token=73bfc4b8-3f15-44b9-a75b-cdb44aec8f4b
--dn-onlyNoFlag to receive relevant Distinguished Names (DN) to update the private.conf file, without generating certificates.--dn-only
--subject-dnYes

The subject of the requested certificate includes the Distinguished Name (DN) consisting of CN, OU, O, L, S, C attributes. The hostname of the requesting client is specified as CN.

--subject-dn="CN=myhost, OU=IT Operations, O=SOS,  L=Berlin, S=Berlin, C=DE"
--sanYes

The Subject Alternative Name (SAN) specifies the hostname of the requesting client and optionally variations of the hostname, e.g. the domain part (FQDN). Alternative hostnames are separated by comma.

--san="myhost, myhost.example.com"
--key-aliasYes

Alias name used when storing the requested private key and certificate to in the target keystore.

--key-alias="MyKeyAlias"
--ca-aliasYes

Alias name used when storing the requested CA certificate in both , the target keystore and truststore.

--ca-alias="MyTrustedCertificateAlias"




--target-keystoreYes

Path to the keystore to in which the requested private key and certificate should be stored.

--target-keystore=/var/sos-berlin.com/js7/controller/var/config/private/https-keystore.p12
--target-keystore-typeNo

Type of the keystore used. Supported values include: PKCS12 (default),
JKS (deprecated).

--target-keystore-type=PKCS12
--target-keystore-passNo

Password for access to the keystore.

--target-keystore-pass="YourKeystorePassword"
--target-keystore-entry-passNo

Password for the requested private key that should be added to the keystore.

--target-keystore-entry-pass="YourKeystoreEntryPassword"




--target-truststoreYes

Path to the truststore to which the trusted CA certificate should be stored.

--target-truststore=/var/sos-berlin.com/js7/controller/var/config/private/https-truststore.p12
--target-truststore-typeNo

Type of the truststore used. Supported values include: PKCS12 (default),
JKS (deprecated).

--target-truststore-type=PKCS12
--target-truststore-passNo

Password for access to the truststore.

--target-truststore-pass="YourTruststorePassword"

--helpNoDisplays usage information, this option has to be specified as the only command line option and has no value.


Explanation:

  • Arguments qualified as required have to be used with any requests request made to the JOC Cockpit to create a private key and certificate.
  • The --joc-uri argument specifies the URL for JOC Cockpit. When used with the HTTPS protocol then check the next section for additional arguments.
  • The --target-keystore is located in the Controller or Agent instance's ./config/private directory.

  • The --dn-only argument if present adds related DNs to the private.conf file in the Controller or Agent instances' ./config/private directory. No certificates/keys are generated.

...

The following arguments are used in addition to standard arguments in case that if the JOC Cockpit is has been set up for HTTPS connections:

Expand
titleList of Arguments for use with JOC Cockpit HTTPS Connections
ArgumentRequiredDescriptionExample
--source-truststoreNo

Path to the truststore holding the trusted certificate(s) to connect to JOC Cockpit by HTTPS.

--source-truststore=/home/sos/public/js7-truststore.p12
--source-truststore-typeNo

Type of the truststore used. Supported values include: PKCS12 (default),
JKS (deprecated).

--source-truststore-type=PKCS12
--source-truststore-passNo

Password for access to the truststore.

--source-truststore-pass="YourTruststorePassword"
--source-certificateNo

Path to a certificate file holding the JOC Cockpit server authentication certificate.

--source-certificate=/home/sos/public/js7-joc-cockpit.crt
--source-ca-certNo

Path to the CA certificate file(s) that are used to verify the JOC Cockpit server authentication certificate. A number of paths can be specified, separated by comma.

--source-ca-cert="/home/sos/public/intermediate_ca.crt, /home/sos/public/root_ca.crt"


Explanation:

  • An HTTPS connection to JOC Cockpit requires to verify verification of the JOC Cockpit Server Authentication Certificate.
  • The --source-truststore-* arguments are used to specify a truststore that holds the Root CA Certificate and optionally any Intermediate CA Certificates involved in signing the JOC Cockpit Server Authentication Certificate.

  • The --source-certificate and --source-ca-cert arguments are used as an alternative to --source-truststore-* arguments in case that JOC Cockpit Server Authentication Certificates are available from individual files instead of being available from a common truststore. Supported certificate formats include PEM.

...

The following arguments are used in addition to HTTPS connection arguments in case that if the JOC Cockpit is has been set up for JOC Cockpit - HTTPS Mutual Authentication.

Expand
titleList of Arguments for use with JOC Cockpit HTTPS Connections using Mutual Authentication
ArgumentRequiredDescriptionExample
--source-keystoreNo

Path of the keystore holding the client's private key and certificate for client authentication.

--source-keystore=/home/sos/private/js7-keystore.p12
--source-keystore-typeNo

Type of keystore used. Supported values include: PKCS12 (default),
JKS (deprecated).

--source-keystore-type=PKCS12
--source-keystore-passNo

Password for access to the keystore holding the private key for client authentication.

--source-keystore-pass="YourKeystorePassword"
--source-keystore-entry-passNo

Password for the private key entry in the keystore.

--source-keystore-entry-pass="YourKeystoreEntryPassword"
--source-private-keyNo

Path to the private key file holding the client authentication private key.

--source-private-key=/home/sos/private/client.key


Explanation:

  • An HTTPS connection to JOC Cockpit with mutual authentication requires:
    • to verify verification of the JOC Cockpit Server Authentication Certificate by the requesting client and
    • to verify the verification of the Client Authentication Certificate of the requesting client by the JOC Cockpit.
  • The --source-keystore-* arguments are used to specify a keystore that holds the client's private key and certificate for client authentication.

  • The --source-private-key argument is used as an alternative to --source-keystore-* arguments in case that if the private key is available from an individual file instead of a keystore.

...

  • the cert argument for the Instance Start Script is used to build the Java classpath and to start the Java executable.
  • The --token argument specifies the one-time token to connect to JOC Cockpit.
  • The --joc-uri argument specifies the URL for JOC Cockpit.
  • If no additional arguments are used then the Command Line Client determines default values for the Keystore and Truststore from the instances' ./config/private/private.conf configuration file, including defaults for the DN and for the SAN of the certificate.

...