Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Enabling encrypted communication between nodes

Updated on March 15, 2022

For on-premises deployments, enable encryption for communication among nodes to prevent unauthorized access to the data that is transported across node clusters.

Enabling encryption between nodes secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. Node encryption is useful when compliance rules require all intracluster communication to be encrypted, such as when working under HIPAA regulations.

Enabling encryption involves the following high-level steps:

  1. Creating the keystore.jks and truststore.jks files

    Enabling encryption between nodes secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. Create a keystore.jks for the private key and the associated certificate or certificate chain.

  2. Uploading the keystore and truststore files

    Enabling encryption between nodes secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. Upload a keystore.jks for the private key and the associated certificate or certificate chain.

  3. Enabling encryption

    Enabling encryption between nodes secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. To enable encryption between nodes, use dynamic system settings.

  4. Restarting nodes

    Enabling encryption between nodes secures the data that is transferred across nodes so that it cannot be accessed by unauthorized hosts. To complete node encryption between nodes, restart nodes.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us