Note: This document is applicable only for CloudCache R2. See CloudCache Versions.
CloudCache R2 ships with a self-signed SSL certificate. The communication between Backup Proxy and CloudCache R2 takes place using a secured TLS. However, Backup Proxy cannot verify the self-signed certificate.
For enhanced security, you can use your own signed SSL certificates. The benefit of using a signed certificate is that the Backup proxy can verify the SSL certificate, which cannot be done for the self-signed certificate.
You must have the SSL certificate and the key file for your domain name.
The SSL certificate file typically has a file extension of .crt, and the key file typically has a file extension of .key.
Contact your network administrator for these files.
Additionally, the root-CA certificate of the certificate authority (CA) must be added to the trust pool of the Backup Proxy server.
It is a two-step process:
Backup Proxy configuration
Log in to the Backup Proxy server, open a terminal, and follow these steps:
Open the following file in any editor:
Locate the following flag and set its value to true:
See the following table for the possible values of this flag and the impact
|Value of Flag
Even though the communication between Backup proxy and CloudCache is over SSL, the CloudCache certificate is not verified.
This is the default option because you will need to provide your certificate and key to enable the certificate validation.
The most secure setting where the communication between Backup proxy and CloudCache uses SSL and the CloudCache certificate is verified.
Restart the Backup Proxy service with the following command:
service phoenix restart
Before you begin, Take note of the path where you saved the certificate and the key file. See Prereqisites.
Log into the CloudCache server, launch a terminal and follow these steps:
- Open the following file in any editor:
The content of this file will be as follows:
Locate the following lines in this file:
Enter the complete path of the certificate file and key as follows:
Finally, save the configuration file and restart the CloudCache service as follows:
service Druva-EnterpriseWorkloads restart