To reduce the errors that customers receive while logging into the SMI, customers might want to install their own vendor signed certificates on their Messaging systems. These certificates are signed by a certificate authority (CA) and are built for a particular system name, that is, fully qualified domain name.
The Certificate Signing Request (CSR) Web page enables you to manage the CSRs present on the server. The customer can generate a CSR to send to their CA, that is, Entrust, VeriSign, and so on. If there are outstanding requests in etc/opt/ecs/certs/signing-requests, the system displays the CSR Web page. If there are no outstanding signing requests, the system displays the CSR - Form Web page. The system allows a maximum of four certificate-signing requests to be outstanding at any given point of time.
Procedure
- On the Administration menu, click .
- Complete the fields with the appropriate information. For more information, see Certificate Signing Request - Form field descriptions.
If there are outstanding certificate service requests, click New Request and complete the fields.
- Click Generate Request.
The system displays the Certificate Signing Request - Display Web page. You must send the certificate output from the Certificate Signing Request - Display Web page to the CA.
- Copy and paste a portion of the CSR data, from the Begin Certificate Request area to the End Certificate Request area, into a notepad and save the notepad.
- Click Continue.
- Send the notepad document to the CA.
The CA vendor sends a Messaging certificate file to the customer. The certificate file includes the .pem or .crt extension. Messaging voice mail uses this certificate. If you install this certificate, the system eliminates the error seen by customers when the customers log in to the Messaging SMI.
The certificates are chained certificates. To install a chained certificate, you must install the CA Root certificate. Some certificate authorities, such as VeriSign require you to install an Intermediate certificate. After you load the Root certificate and Intermediate certificate, if required, you can install the Messaging certificate.
The customer must download the Root certificate and install this certificate before installing other certificates on the Messaging system. The following links are for the Root certificates of VeriSign and Entrust.
Note Larger customers might have a contract with the vendor and therefore have direct access to the Root and Intermediate certificates. The customer follows vendor directions on how to download the Root certificate. If an Intermediate certificate is required, the website of the vendor provides information on how to obtain the Intermediate certificate.
VeriSign: http://www.verisign.com/repository/roots/root-certificates/PCA-3G2.pem. Copy the certificate information in the PCA-3G2.pem file.
Entrust: https://www.entrust.net/downloads/root_request.cfm. Enter your name, company name, and email address and then select the Entrust Root CA check box and select the Server/Host Type as Apache (OpenSSL). Click Accept. After you receive the email, copy the certificate information in the PCA-3G2.pem file.
- After the customer has all the certificates, Root, Intermediate, and Messaging, the customer can download these certificates to the Messaging system. The customer must first copy these certificates to the /var/home/ftp/pub directory.
To copy these certificates to the /var/home/ftp/pub directory, see Downloading files.