About this task
During MPP installation, the installation script creates a symbolic link to this file, which Apache uses to access the certificate. If that symbolic file does not exist, a connection cannot be established between the MPP and the EPM. Therefore, you must also verify that the symbolic link exists on the MPP.
Procedure
- Compare the MPP certificate to the one on the EPM by entering the curl http://EPM-server/cert.pem command, where EPM-server is the domain name or IP address of the system where the primary EPM software is installed.
- At the Linux command
line prompt, enter the cat $AVAYA_MPP_HOME/web/ssl.crt/vpms.crt command.
The system should respond with a message similar to the following:
-----BEGIN CERTIFICATE----- MIICfDCCAeWgAwIBAgIBADANBgkqhkiG9w0BAQQFADA5MQwwCgYDVQQLEwNNUFAx DjAMBgNVBAoTBUF2YXlhMRkwFwYDVQQDExBtbHZvaWNlcG9ydGFsLWE5MB4XDTA1 DAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQCU36+QLX56yDK0l4wkb8Ai VQQKEwVBdmF5YTEZMBcGA1UEAxMQbWx2b2ljZXBvcnRhbC1hOTCBnzANBgkqhkiG zPEZEzz12iYGBB7EzvN8WsbUVU+7hN1ojNsidt25gTu8ol2Pnz4pnonGAc3xowAo 9w0BAQEFAAOBjQAwgYkCgYEAt9166cK3sMldlsq83aFwwykCeItEA/XDZbyYewKP z2T6RDS2TD+EwDKQjuxo8h1upDVFgherJdK4Ks+PvbnN6yIxW39wOU8Gl3JbWJgR 1WrRVjelUg5hpVcHxkdkRynkmM8bJBvaohqS5NMiygBfUXaz+Qx7wWVevkM7qdeM MDkyOTE2MTExM1oXDTE1MDkyNzE2MTExM1owOTEMMAoGA1UECxMDTVBQMQ4wDAYD GMMCAwEAAaOBkzCBkDAdBgNVHQ4EFgQUUH67bdY3lHOTZVx6u34wj1roPvwwYQYD WSz+QXogX265wzyYXZDQuGZ9hRm0nhQjXv20C6EfNK8T+g03/NfqqxqjJdKrelya VR0jBFowWIAUUH67bdY3lHOTZVx6u34wj1roPvyhPaQ7MDkxDDAKBgNVBAsTA01Q UDEOMAwGA1UEChMFQXZheWExGTAXBgNVBAMTEG1sdm9pY2Vwb3J0YWwtYTmCAQAw WZg0Cm00qzzk9qWf9SKpbg== -----END CERTIFICATE----- - Change to the directory in which the SSL certificate from the EPM resides by entering the cd $AVAYA_MPP_HOME/web/ssl.crt/ command.
- List all files in this
directory by entering the ls -al command.
You should see a symbolic link to the vpms.crt file, similar to the following entry:
lrwxrwxrwx 1 ^sroot^root^ 8 Oct 7 18:21 36c998fa.0 -> vpms.crtThe "l" at the beginning and the"-> vpms.crt" text at the end indicate that the symbolic file has been created. In this example, the file is named36c998fa.0.
Note:This file is created and named automatically by the installation script, using a hash security encryption scheme.
- Did the system respond
correctly to both these commands?
If yes, an SSL certificate is correctly installed on the MPP. No further action is required, unless you want to ensure that the certificate is valid. In that case, you can reinstall the certificate.
If no, the SSL certificate either is not installed or is invalid. Try reinstalling the certificate.