12-09-2019 02:10 AM
Hello
On my CUCM servers I see that the following certificate ( VeriSign_Class_3_Secure_Server_CA_-_G3) goes to expire on Feb,2020.
So I would like to know what is the goal (usage ) of this certicate ?
And how I can renew ( replace ) this certificate ?
It's really importante to replace it or not ?
I understand this certicate is automaticvally implement by Cisco during the CUCM installation.
Also I have the same certificate UCCX solution.
Many thanks for your help.
Regards,
Christophe/
Solved! Go to Solution.
12-09-2019 05:50 AM
It's a public cert installed in Tomcat-Trust that comes pre-installed on Cisco apps for "Call Home Server Certificate" feature in case you need to communicate with Cisco Home server. If you are not using that feature you do not require this cert and can just remove it. If you need it you'll need to download the new root cert from VeriSign and install into Tomcat-trust.
12-09-2019 05:50 AM
It's a public cert installed in Tomcat-Trust that comes pre-installed on Cisco apps for "Call Home Server Certificate" feature in case you need to communicate with Cisco Home server. If you are not using that feature you do not require this cert and can just remove it. If you need it you'll need to download the new root cert from VeriSign and install into Tomcat-trust.
12-09-2019 05:55 AM
Hi Chris,
Thanks for your answer.
Perfect for my comprehension.
Have good day.
Christophe/
12-09-2019 07:14 AM
Hi Chris,
Is this documented somewhere? I've been looking for the past month.
12-23-2019 09:03 AM
01-10-2020 06:09 AM
Hi Chris,
I have got the same expiration notification on our Call Manager. I would like to renew the VeriSign_Class_3_Secure_Server_CA_-_G3 certificate. Would you please let me know where I can download it.
I only found the root certificates to download on the Symantec web site.
Thanks in advance
Vitali
01-14-2020 03:20 AM
You can use
-----BEGIN CERTIFICATE-----
MIIFODCCBCCgAwIBAgIQUT+5dDhwtzRAQY0wkwaZ/zANBgkqhkiG9w0BAQsFADCB
yjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMjAwNiBWZXJp
U2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxW
ZXJpU2lnbiBDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0
aG9yaXR5IC0gRzUwHhcNMTMxMDMxMDAwMDAwWhcNMjMxMDMwMjM1OTU5WjB+MQsw
CQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNV
BAsTFlN5bWFudGVjIFRydXN0IE5ldHdvcmsxLzAtBgNVBAMTJlN5bWFudGVjIENs
YXNzIDMgU2VjdXJlIFNlcnZlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAstgFyhx0LbUXVjnFSlIJluhL2AzxaJ+aQihiw6UwU35VEYJb
A3oNL+F5BMm0lncZgQGUWfm893qZJ4Itt4PdWid/sgN6nFMl6UgfRk/InSn4vnlW
9vf92Tpo2otLgjNBEsPIPMzWlnqEIRoiBAMnF4scaGGTDw5RgDMdtLXO637QYqzu
s3sBdO9pNevK1T2p7peYyo2qRA4lmUoVlqTObQJUHypqJuIGOmNIrLRM0XWTUP8T
L9ba4cYY9Z/JJV3zADreJk20KQnNDz0jbxZKgRb78oMQw7jW2FUyPfG9D72MUpVK
Fpd6UiFjdS8W+cRmvvW1Cdj/JwDNRHxvSz+w9wIDAQABo4IBYzCCAV8wEgYDVR0T
AQH/BAgwBgEB/wIBADAwBgNVHR8EKTAnMCWgI6Ahhh9odHRwOi8vczEuc3ltY2Iu
Y29tL3BjYTMtZzUuY3JsMA4GA1UdDwEB/wQEAwIBBjAvBggrBgEFBQcBAQQjMCEw
HwYIKwYBBQUHMAGGE2h0dHA6Ly9zMi5zeW1jYi5jb20wawYDVR0gBGQwYjBgBgpg
hkgBhvhFAQc2MFIwJgYIKwYBBQUHAgEWGmh0dHA6Ly93d3cuc3ltYXV0aC5jb20v
Y3BzMCgGCCsGAQUFBwICMBwaGmh0dHA6Ly93d3cuc3ltYXV0aC5jb20vcnBhMCkG
A1UdEQQiMCCkHjAcMRowGAYDVQQDExFTeW1hbnRlY1BLSS0xLTUzNDAdBgNVHQ4E
FgQUX2DPYZBV34RDFIpgKrL1evRDGO8wHwYDVR0jBBgwFoAUf9Nlp8Ld7LvwMAnz
Qzn6Aq8zMTMwDQYJKoZIhvcNAQELBQADggEBAF6UVkndji1l9cE2UbYD49qecxny
H1mrWH5sJgUs+oHXXCMXIiw3k/eG7IXmsKP9H+IyqEVv4dn7ua/ScKAyQmW/hP4W
Ko8/xabWo5N9Q+l0IZE1KPRj6S7t9/Vcf0uatSDpCr3gRRAMFJSaXaXjS5HoJJtG
QGX0InLNmfiIEfXzf+YzguaoxX7+0AjiJVgIcWjmzaLmFN5OUiQt/eV5E1PnXi8t
TRttQBVSK/eHiXgSgW7ZTaoteNTCLD0IX4eRnh8OsN4wUmSGiaqdZpwOdgyA8nTY
Kvi4Os7X1g8RvmurFPW9QaAiY4nxug9vKWNmLT+sjHLF+8fk1A/yO0+MKcc=
-----END CERTIFICATE-----
01-16-2020 05:11 PM
Has anyone had any luck with this? I followed the instructions outlined - saved as a .pem file, uploaded to call manager (which said it was successful), then restarted tomcat services as instructed by call manager. After service restart, the only copy of this certificate is this nearly expired one. Do I need to remove the old certificate first?
01-16-2020 05:59 PM
You need to delete the old certificate and then or before (does not matter as long as CN on cert is different) upload the new one into the tomcat-trust store.
01-17-2020 02:20 PM
I have:
I still do not have the new VeriSign_Class_3_Secure_Server_CA_-_G3 Did I miss something?
01-17-2020 03:10 PM
According to SSL cert decoder the CN of the cert posted in the doc is "QuoVadis Root CA 2", do you not see that?
Remember the name of the cert is not that important, it's what trust store it's on that establishes the trust and how other trusted certs use it. When you upload the cert you can always add description to make it easier for yourself to find it later in CUCM.
02-06-2020 05:39 PM
Hi Chris,
In the following Bug ID, there was a description for PLM in addition to CUCM.
There was a statement that PLM was the only way to remove providing COP files.
Bug ID: CSCvs64158
Can I check if the certificate corresponding to PLM is included or deleted?
For example, can it be confirmed with CLI commands?
02-07-2020 05:28 AM
I believe the reference is for standalone PLM server. If you are running standalone reference and need to or want to renew the cert you would need to follow that workaround. If your PLM is colocated with another node such as CUCM then the documented procedure for CUCM applies.
05-12-2020 05:37 AM
02-09-2020 09:14 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide