How To Guides > Edge Cache > Configuring Edge Cache > Preparing & Trusting a Certificate for Encrypted Traffic

Preparing & Trusting a Certificate for Encrypted Traffic

When caching encrypted content, you need to specify a certificate that Edge Cache will use to create and sign a dynamically created certificate on behalf of the server. You will need to ensure that this certificate is trusted by all the computers on your network that will have traffic that passes through Edge Cache. It is recommended that you create a self-signed CA certificate (as opposed to a self-signed certificate without the CA designation) to simplify loading and trusting the certificate by the computers in your network.

How to create a self-signed CA certificate for Edge Cache to use

When using Edge Cache for encrypted traffic, you must create and import a signing certificate in the Certificates and Keys store. This certificate and its corresponding key will be used by Edge Cache to generate and sign dynamic SSL certificates for proxied sites. For all practical purposes, this certificate becomes a root certificate and you become a Root CA.

How to tell client computers to trust the installed certificate

If the browsers in your network don't trust the certificate, you may get a warning or the sites may fail to load. In this case, each computer needs to import the certificate so that the certificate will be trusted when negotiating with Edge Cache over SSL.

You will need to export the certificate from the appliance and import it to the desired computers.

 

< Previous: Configuring Edge Cache Introduction     |      Next: Configuring DNS >