Adding a server and application certificate

The system displays the Server/Application Certificates Web page.

The Messaging certificate file must be in the /var/home/ftp/pub directory and the file must have a .pem or .crt extension

The system displays the Server/Application Certificates - Add Web page.

The certificate name must be either a PKCS#12 file or a file in pem format.

The system verifies the following:

• The certificate name has a .pem or .crt extension. If the certificate name has a different extension, the system deletes the extension and replaces the extension with a .crt extension.

• The certificate name is unique and does not already exist.

• The certificate is not a duplicate certificate with a new name.

After successful verification, the Server/Application Certificates Web page displays the issued-to, issued by, and date of expiration information for each of the added certificates in the chain.

If the file does not contain a valid certificate, the system displays an error message instead of the certificate content.

Note

The system does not prompt you to enter a file name to store the certificate. By default, the file name is server.crt.

In the case of single server and application certificate chain, the server sub-directory of a repository is limited to a single file for a single certificate chain and the file is server.crt. This certificate represents an identity and only one identity is supported. The system overwrites the existing server.crt file.

After successful installation of server certificate, the SSL client, for example browser of client machine accessing the SMI , will prompt you regarding the change. After you accept the change, the system displays the previously accessed page.

Note

If you fail to install a certificate in one repository, this failure does not affect the installation in other repositories.