During the CMS security certificate installation, an error message is displayed indicating an invalid certificate, as shown in Figure 9-2.
Figure 9-2 Invalid CMS security certificate
To ensure that the CMS security certificate is valid, it is recommended that you make a new CMS security certificate.
If you are sure that the CMS security certificate is valid, upload the CMS security certificate to the specified directory.
If only one CMS server is deployed in a single-node system
Export the newly made CMS security certificate and upload it to CMS_Release/webapps/CMS/ssl.
keytool -keystore tomcatKeyStore -export -alias eSpaceCMS -file bmecert.cer
cp -r bmecert.cer /home/cms/CMS_Release/webapps/CMS/ssl
For details, see Creating a Security Certificate.
If several CMS servers are deployed in a cluster
Export the newly made CMS security certificate and upload it to CMS_Release/webapps/CMS/ssl on each CMS server.
openssl req -x509 -days 3650 -key server.key -in server.csr > server.crt
put /opt/lb/conf/server.crt /home/cms/CMS_Release/webapps/CMS/ssl/bmecert.cer
To upload a file to a CMS server, remotely connect to the CMS server first.
For details, see Uploading the CMS Security Certificate to a CMS Server.
If the fault still persists, obtain help through the channels described in Help Channels.
The CMS security certificate is not uploaded to CMS_Release/webapps/CMS/ssl.
The CMS security certificate that has been uploaded to CMS_Release/webapps/CMS/ssl is invalid.