Configure secure communication with two-way TLS (SSL) authentication
This task describes the steps required to set up secure communication with two-way TLS (SSL) authentication in your LoadRunner Professional environment.
-
Set up the CA and TLS certificates
- Create a Certificate Authority (CA) certificate or ensure that you have a valid existing CA certificate.
-
Create or select a TLS certificate.
-
Install the CA and TLS certificate on all relevant LoadRunner Professional machines in your system.
For details, see Configure secure communication with TLS (SSL).
-
Determine which machine in your system is the server for client-server communications. For details, see Two-way TLS (SSL) authentication.
-
Activate client authentication on the machine acting as the server.
Do one of the following:
- Use the Network and Security Manager command line tool to activate authentication for the host machine that is acting as the server. Set -check_client_cert to 1. .
-
When working over a firewall, in the Agent Configuration Over Firewall Settings Dialog Box, select Use Secure Connection (SSL) and enter relevant details.
-
Configure Authentication Settings in Controller.
In Controller, select the CA and TLS certificates to be used for the scenario run. For details, see Authentication Settings tool.
-
Activate server authentication on client machines (optional).
If you want the client machines to validate the server certificate, set this option for each client machine.
Do one of the following:
- Use the following Network and Security Manager command line from a single location to activate server authentication on all relevant host machines: set -check_server_cert to High for the highest level of security. For more information, see -check_server_cert.
- On each client machine in your system, enable the Use Secure Connection (SSL) option in the Agent Configuration Settings dialog box, and set the Check Server Certificates level.
Note: When provisioning Load Generators on the cloud, the certificates will be taken from Controller and automatically copied to the Load Generators, so the communication will be secure by default. For details about working with load generators on the cloud, see Load generators on the cloud.
