You can change whether the CloudBoost appliances use the default self-signed certificate or a CA-signed SSL certificate. See below for more information.
Solved! Go to Solution.
Because self-signed SSL certificates are less secure than those signed by a trusted Certificate Authority, self-signed certificates should be used only for test deployments.
In production environments, you should use an SSL certificate signed by a trusted Certificate Authority. The CA-signed certificate must be suitable for SSL server usage and must cover all the host names in the deployment.
If you deploy an instance for testing and later decide to move it to production, you can update the SSL certificate.
Option | Description |
---|---|
Use the default self-signed certificate | This is selected by default. |
Provide a CD-signed certificate | Upload a CA-signed wildcard certificate in the form of a .p12 or .pfx file and if necessary, type the key file password. |
4. Click Update Configuration.
Because self-signed SSL certificates are less secure than those signed by a trusted Certificate Authority, self-signed certificates should be used only for test deployments.
In production environments, you should use an SSL certificate signed by a trusted Certificate Authority. The CA-signed certificate must be suitable for SSL server usage and must cover all the host names in the deployment.
If you deploy an instance for testing and later decide to move it to production, you can update the SSL certificate.
Option | Description |
---|---|
Use the default self-signed certificate | This is selected by default. |
Provide a CD-signed certificate | Upload a CA-signed wildcard certificate in the form of a .p12 or .pfx file and if necessary, type the key file password. |
4. Click Update Configuration.