|
The MPP and EPM use SSL mutual authentication to protect the data exchanged between the Web Services on both servers. Mutual authentication requires that certificates be exchanged between the servers. If the certificates do not exist or are corrupted, the EPM is not able to establish contact with the MPP.
MPP configuration for mutual authentication requires that:
The MPP has its own key and certificate. This certificate is used when the MPP Web services or the Media Server Service Menu is accessed. During the installation of MPP software, you are prompted to either provide the certificate or have the installation create one for you.
The MPP has a valid copy of the EPM SSL certificate downloaded to register the EPM as a recognized certificate authority. The EPM SSL certificate is downloaded during MPP software installation. However, if the MPP SSL certificate and key appear valid and you are still having trouble with exchange of data between the MPP and the EPM, you can validate, and redownload the EPM SSL certificate.
The MPP configuration file, mpp.conf, must have the correct paths to the SSL certificate and key files. The httpd daemon uses this file at startup to establish communications between the MPP and the EPM. If the paths in this file are not valid, the two servers cannot establish secure communications.
For more information about Apache and SSL, see SSL/TLS Strong Encryption.