Securing Communications Process to MF Directory Server using TLS

ESCWA can communicate to a remotely hosted MF Directory Server and its enterprise server instance. The instances use a Communication Processes to connect to the MF Directory Server. If you have configured your MF Directory Server to use TLS then you need to configure the Communications Process to communicate as a TLS enabled client. See Communications Process for more information.

Communications between Communications Process and a Directory Server can be secured by configuring TLS settings on the Directory Server's Connection Properties page. See Connection Properties for more information. Check Enable TLS, and then check Use Custom Certificates. Specify your certificate and keyfile information.

Note: The MF_ROOT_CERT environment variable must be set to point to the file containing the CA certificate(s) needed to verify the certificate used by the MF Directory Server.

The Directory Server does not support authentication to a Communications Process using a client certificate, so it will not be able to connect to a Communications Process TLS-enabled listener that is configured to require client certificate authentication.