Versions Compared

Key

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

...

JS7 - Deployment of Scheduling Objects makes use of signing certificates Signing Certificates to digitally sign workflows and other objects. Use of certificates for signing is not related to use of certificates to secure connections such as using HTTPS.

  • Certificates for the specific use of code signing should must be used.
  • Users choose which approach they want to follow:
    • Creating self-signed certificatesCertificates.
    • Creating CA-signed certificatesCertificates.

Rollout of certificates to Controllers and Agents depends on the following choice:

...

  • The -days argument optionally specifies the validity period of the Certificate.
  • The -signkey option specifies the location of the Private Key file created from the previous step.
  • The -in option specifies the location of the Certificate Signing Request file created from the previous step.
  • The -out option specifies the location of the resulting Certificate file.
  • The -extfile option specifies a number of extensions recommended for use with Signing Certificates. 
  • The following files will be created with this step:
    • The <key_name>.crt file will hold the self-signed Certificate.

Self-signed Certificates must be copied to the <data>/config/private/trusted-x509-keys directory of Controller and Agent instances.

Anchor
ca_signed_certificates
ca_signed_certificates
Creating CA-signed Certificates

...

  • Explanations are similar to Creating self-signed Certificates with a few exceptions.
  • The -days option specifying the validity period of the Certificate should be longer than the validity period of individual certificates.
  • The -extfile option specifies the Basic Constraint CA:TRUE which is required for a CA. Key Usage is limited to signing certificates.
  • The following files will be created with this step:
    • The signing-ca.crt file will hold the CA Certificate.

The CA Certificate must be copied to the <data>/config/private/trusted-x509-keys directory of Controller and Agent instances.

Anchor
creating_signing_certificates
creating_signing_certificates
Creating Signing Certificates

...

Users can run the following commands from a Shell shell and replace the value of the key_name environment variable with a name of their choice that is used when creating related files:

...

  • Explanations are similar to Creating self-signed Certificates with a few exceptions:
    • The -days option specifying the validity period of the Certificate should be shorter than the validity period of the CA Certificate.
    • The -in option specifies the location of the Certificate Signing Request.
    • The -CA option specifies the location of the CA Certificate file.
    • The -CAkey option specifies the locatioon location of the CA Private Key file.
    • The -extfile option specifies the Key Usage being limited to code signing.
  • The following files will be created with this step:
    • The signing-ca.crt file will hold the Signing Certificate..

The Signing Certificate file does not require to be deployed to Controller and Agent instances. Instead, the CA Certificate file is deployed to Controller and Agent instances.


---------------------------------------------------------------------------------------------

...