Connection security overview
HCL Workload Automation provides a secure, authenticated, and encrypted connection mechanism for communication based on the Secure Sockets Layer (SSL) protocol, which is automatically installed with HCL Workload Automation.
HCL Workload Automation also provides default certificates to manage the SSL protocol that is based on a private and public key methodology.
If you do not customize SSL communication with your certificates, to communicate in SSL mode, HCL Workload Automation uses the default certificates that are stored in the default directories. However, in a production environment, it is recommended that you customize SSL communication with your own certificates as explained in the following scenarios.
You can customize SSL communication with your certificates according to your security requirements.
- Scenario: Connection between the Dynamic Workload Console and the HCL Workload Automation component that has a distributed connector.
- Scenario: Connection between dynamic agents and the master domain manager or dynamic domain manager.
- Scenario: SSL Communication across the HCL Workload Automation network.
- Scenario: HTTPS for the command-line clients.
- truststore
- In security, a storage object, either a file or a hardware cryptographic card, where public keys are stored in the form of trusted certificates, for authentication purposes in web transactions. In some applications, these trusted certificates are moved into the application keystore to be stored with the private keys.
- keystore
- In security, a file or a hardware cryptographic card where identities and private keys are stored, for authentication and encryption purposes. Some keystores also contain trusted or public keys.