Setting Up Secure Communications

Restriction: This topic applies only when the Enterprise Server feature is enabled.

To set up secure communications, you need the following:

For machine on which the server operates, a certificate and a private key file for the server.
Typically these are issued by a trusted Certifying Authority (CA). To set up secure communications, you need to know the path location where these files are stored.
The pass phrase for the server certificate and keyfile.
Note: You can use the Micro Focus Vault Facility to store a secret for the certificate and keyfile pass phrases. This takes the following form:
```
mfsecret:configuration-name:secret-path
```
or:
```
mfsecret::secret-path
```
or:
```
mfsecret:secret-path
```
For machines that access the listener, the CA's root certificate.
Root certificates for many trusted authorities are installed by default with many web browsers.

The process you use to set up secure communications for an enterprise server instance is outlined below:

Install the certificate and a private key file on the machine running Enterprise Server, and note the path.
For the Enterprise Server instance to configure, create a secure listener and configure it to use the key file that you installed.
Start the server and the listener, and configure the private key file's pass phrases.
You can set the certificate and keyfile pass phrases either in a configuration file, or you can enter them manually whenever you start the server.
On machines that use the listener, if required, configure the CA root certificate.

Steps 2, 3, and 4 are described in detail in this Help.