PDF(181.3 KB) View with Adobe Reader on a variety of devices
ePub(196.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(207.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:May 25, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the advancement made in certificate management for Cisco Unified Communications Manager (CUCM) implemented in version 11.x.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software versions:
CUCM version 220.127.116.1100-6
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
CUCM certificate management helps Unified Communications or security administrators take advantagesmanage certificates more efficiently. Advantages of the enhancement made include a decreased time during removal of unwanted of expired certificates in CUCM and IM&Presence.
Prior to CUCM version 11, this message appeared if a certificate is deleted.
The certificate gets deleted only from the node on which the delete operation is initiated.
If the same certificate is not deleted in other nodes, the deleted certificate gets populated back in the node where it was initially deleted. This is due to the certificate monitoring service called Certificate Change Notification. As a best practice in older versions of CUCM, the Certificate Change Notification service is stopped on all the CUCM nodes before certificate deletion. Another drawback in older versions is the requirement to log in to the OS administration section of each node in order to delete a single unwanted or expired certificate, which becomes tedious and time consuming especially for a big cluster.
Starting at CUCM version 11.0 or higher, any unwanted or expired certificates that are deleted from the current node are also deleted from all other nodes within the cluster.
The enhancement was included to address these defects:
CSCto86463 - Deleted certificates reappear, unable to remove certificates from CUCM
CSCus28550 - Cert Management Enhancement to delete a certificate from all nodes
Frequently Asked Questions
Q. What are the type of certificates included in this enhancement?
A. For Cisco Unified Communications Manager:
For Cisco Unified Communications Manager IM & Presence:
Q. What happens at the backend for this enhancement?
A. As soon as a certificate is deleted in any one of the CUCM nodes:
Certificate is deleted from the local node
Platform event triggers deletion of the same certificate to all other nodes.
Once a certificate is deleted via the OS Administration page in a node, log in to other nodes and check if the certificate is present or not. If a deleted certificate is not deleted from all the nodes, check the logs generated through the instance of certificate deletion.
IPT Platform CertMgr Logs
In a common working scenario, these are the expected logs.
Platform-event is seen in other nodes (other than the node where the certificate deletion was initiated). In this example, a tomcat-trust certificate named CUCMSUB1.pem was deleted from the publisher, diplaying this on the subscriber’s syslog.
Aug 6 20:20:47 CUCMSUB1 user 6 ilog_impl: Received request for platform-event (--no-wait platform-event-clusterwide-certificate-delete HOSTNAME=CUCM-PUB UNIT=tomcat-trust NAME=CUCMSUB1.pem)
IPT Platform CertMgr Logs
In the CertMgr logs, the records confirm that the certificate is on queue for deletion from the database entries.
2016-08-06 21:22:06,151 INFO [main] - IN -- CertDBAction.java - deleteCertificateInDB(certInfo) -
Certificate : Not Printing huge Certificate String..
IPV4Address : 10.106.99.196
TimeToLive : NULL
UNIT : tomcat-trust
TYPE : trust-certs
ROLE : null
RoleMoniker : null
SERVICE : null
ServiceMoniker : null
2016-08-06 21:22:06,151 INFO [main] - DB - Certifciate Store Plugin Handler is :com.cisco.ccm.certmgmt.db.CertDBImpl
2016-08-06 21:22:06,156 INFO [main] - IN -- CertDBImpl.java - deleteCertificate(certInfo) –
SQL command triggered for deletion of the certificate can be seen in the CertMgr logs.
2016-08-06 21:22:08,980 DEBUG [main] - Delete query of CERTIFICATEPROCESSNODEMAP :DELETE FROM CERTIFICATEPROCESSNODEMAP WHERE FKCERTIFICATE="cdd0365a-2d17-3483-4d00-1bf08f942cf5" AND SERVERNAME = "CUCMSUB1"
2016-08-06 21:22:08,980 DEBUG [main] - execute(DELETE FROM CERTIFICATEPROCESSNODEMAP WHERE FKCERTIFICATE="cdd0365a-2d17-3483-4d00-1bf08f942cf5" AND SERVERNAME = "CUCMSUB1")
From the CertMgr logs, the entries confirm that the certificate is deleted from the FILE-SYSTEM (certificate with pem or der extensions).