TLS (SSL) Certificates

Most SnapLogic API requests can be sent to the SnapLogic cloud endpoint. The SnapLogic cloud runs with a signed TLS (SSL) certificate. The client sending the HTTP request will validate the CA certificate to verify the validity of the certificate.

Some SnapLogic API requests can be sent to the Groundplex nodes directly, including requests for Ground-triggered Pipelines and requests to the FeedMaster nodes for Ultra Pipelines. The Snaplex nodes run with self-signed certificates. A load balancer must be installed to handle the incoming requests to the Groundplex nodes. The load balancer can be configured with the customer's TLS (SSL) certificate. The clients see the certificate exposed by the load balancer.

  • If the load balancer is configured with a custom TLS (SSL) certificate and configured to terminate TLS (SSL) connections, you do not have to change the TLS (SSL) certificate on the Groundplex nodes. The Groundplex nodes can run using the default SnapLogic-generated certificate, which is the recommended configuration.

If the certificate cannot be changed on the load balancer, choose one of the following methods to allow the HTTP clients to verify the authenticity of the Snaplex nodes when sending these requests:

  • Allow all certificates: If running on a trusted network, the HTTP client can be configured to allow all certificates. 
  • Update the Snaplex nodes to run with a signed certificate: This requires updating all the Snaplex nodes to run with a signed certificate provided by the customer. The keystore would have to be updated on each Snaplex node and the service restarted to enable this option. Either a wildcard certificate or a unique certificate per node would have to be used to enable this option.
  • Trust org specific CA certificate: Each Snaplex node runs with a self-signed certificate which is signed with an Org-specific CA certificate. You can download this Org certificate and add it to its trust store to allow trusted communication with any node in the Org. To download the certificate, go to the details of a Triggered task and click on the Download the CA certificate for your SnapLogic organization option.

Configuring a Snaplex Node to Host a CA-signed TLS (SSL) Certificate

Perform the following steps:

  1. (Recommended) On the Snaplex node, create a backup copy of jcc-serverkeys.jks.
    • Linux default:
    • Windows default:

  2. Concatenate all PEM encoded files into a single chain file.
    Linux Example: 

    <CA-SIGNED-PEM> is the CA-signed TLS (SSL) certificate (PEM encoded).
    <CA-INTERMEDIATE-PEM> is the CA intermediate certificate (PEM encoded).
    <CA-ROOT-PEM> is the CA root certificate (PEM encoded).

  3. To ensure that there is not a password associated with the private key file for later operations, use the openssl command.
    Linux Example:

    <PRIVATE_KEY> is the private key used to create the CSR (PEM encoded).

    If there is a password associated with the private key, you must provide it to generate key_no_pass.pem.

  4. Use the openssl command to generate the PFX file.
    Linux Example:

  5. Use the keytool command to import the PFX file into jcc-serverkeys.jks.
    Linux example:

    <PATH-TO-SL-CA-CHAIN-P12> is the absolute path to the sl-ca-chain.p12 file created in Step 4.

  6. Use the SnapLogic Dashboard to restart the Groundplex node to ensure that the node enters a steady state and allow time for running Pipelines to complete.

  7. (Optional) Use the openssl command to verify that the TLS (SSL) certificate served by the node matches the CA-signed TLS (SSL) certificate.
    Linux example:

    <SECURE-PORT> is 8081 (default) for a Groundplex or 8084 (default) for a FeedMaster node.

  8. Repeat Steps 1 through 7 for all applicable nodes.