Print

Validating the MPP configuration file for the SSL certificates

About this task

The MPP configuration file, mpp.conf, contains, among other things, the paths for the SSL certificates, both for the MPP and for the EPM.

importantImportant:

The EPM expects to find the MPP certificate at /var/www/html/cert.pem. If you change this location, the EPM may not be able to find the certificate.

Procedure

  1. Log in to the MPP server whose configuration file you want to validate.
  2. At the Linux command line prompt, enter the cat $AVAYA_MPP_HOME/config/mpp.conf command.

    The system displays the contents of the entire MPP configuration file.

  3. Locate the entry for the MPP SSL certificate and key in the Global section.

    The entry should be identical to the following:

    SSLCertificateKeyFile
    /opt/Avaya/ExperiencePortal/pki/ep_private_key.key
    SSLCertificateFile
    /opt/Avaya/ExperiencePortal/pki/ep_identity_cert.crt
  4. Locate the entry for the MPP SSL certificate and key in the Virtual Host port 9443 section.

    The entry should be identical to the following:

    SSLCertificateKeyFile
    /opt/Avaya/ExperiencePortal/pki/ep_private_key.key
    SSLCertificateFile
    /opt/Avaya/ExperiencePortal/pki/ep_identity_cert.crt
  5. Locate the entry for the MPP SSL certificate and key in the Virtual Host port 10443 section.

    The entry should be identical to the following:

    SSLCertificateKeyFile
    /opt/Avaya/ExperiencePortal/pki/ep_private_key.key
    SSLCertificateFile
    /opt/Avaya/ExperiencePortal/pki/ep_identity_cert.crt
    SSLCertificateChainFile
    /opt/Avaya/ExperiencePortal/pki/ep_cert_chain.crt
  6. Locate the entry for the EPM SSL certificate download.

    This entry should look similar or identical to:

    SSLCACertificatePath "/opt/Avaya/ExperiencePortal/MPP/web/ssl.crt"
  7. If any of these entries are different from what you have actually configured on your system, use a text editor to edit the mpp.conf file to reflect the actual configuration.
  8. If you manually edit the mpp.conf file, you must restart the httpd daemon process to activate the changes:
    1. Stop the httpd daemon process by entering the /sbin/service httpd stop command.

      The system should respond with a message that ends with [OK] to indicate that the service has stopped.

    2. Restart the httpd daemon process by entering the /sbin/service httpd start command.

      The system should respond with a message that ends with[OK] to indicate that the service has started.