PDF(3.2 MB) View with Adobe Reader on a variety of devices
ePub(3.6 MB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(1.3 MB) View on Kindle device or Kindle app on multiple devices
Updated:May 12, 2023
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 procedure to update CUCM connections to AD from a non-secure LDAP connection to a secure LDAPS connection.
Cisco recommends that you have knowledge of these topics:
• AD LDAP Server • CUCM LDAP Configuration
• CUCM IM & Presence Service (IM/P)
The information in this document is based on CUCM release 9.x and higher.
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, ensure that you understand the potential impact of any command.
It is the responsibility of the Active Directory (AD) Administrator to configure AD Lightweight Directory Access Protocol (LDAP) for Lightweight Directory Access Protocol (LDAPS) . This includes the installation of CA-signed certificates that meet the requirement of an LDAPS certificate.
Step 1. After the LDAPS certificate has been uploaded to the AD server, verify that LDAPS is enabled on the AD server with the ldp.exe tool.
Start the AD Administration Tool (Ldp.exe) on the AD server.
On the Connection menu, select Connect.
Enter the Fully Qualified Domain Name (FQDN) of the LDAPS server as the server.
Enter 636 as the port number.
Click OK, as shown in the image
For a successful connection on port 636, RootDSE information prints out in the right pane, as shown in the image:
Repeat the procedure for port 3269, as shown in the image:
For a successful connection on port 3269, RootDSE information prints out in the right pane, as shown in the image:
Step 2. Obtain the root and any intermediate certificates that are part of the LDAPS server certificate and install these as tomcat-trust certificates on each of the CUCM and IM/P publisher nodes and as CallManager-trust on the CUCM publisher.
The root and intermediate certificates that are part of an LDAPS server certificate, <hostname>.<Domain>.cer, are shown in the image:
Navigate to CUCM publisher Cisco Unified OS Administration > Security > Certificate Management. Upload root as tomcat-trust (as shown in the image) and as CallManager-trust (not shown):
Upload intermediate as tomcat-trust (as shown in the image) and as CallManager-trust (not shown):
Note: If you have IM/P servers that are part of the CUCM cluster, you also need to upload these certificates to these IM/P servers.
Note: As an alternative, you can install the LDAPS server certificate as tomcat-trust.
Step 3. Restart Cisco Tomcat from the CLI of each node (CUCM and IM/P) in clusters. Additionally, for the CUCM cluster, verify that the Cisco DirSync service on the publisher node is started.
In order to Restart the Tomcat service, you need to open a CLI session for each node and run the command utils service restart Cisco Tomcat, as shown in the image:
Step 4. Navigate to CUCM publisher Cisco Unified Serviceability > Tools > Control Center - Feature Services, verify that the Cisco DirSync service is activated and started (as shown in the image), and restart the Cisco CTIManager service on each node if this is used (not shown):
Configure Secure LDAP Directory
Step 1. Configure the CUCM LDAP Directory in order to utilize LDAPS TLS connection to AD on port 636.
Navigate to CUCM Administration > System > LDAP Directory. Type the FQDN or the IP address of the LDAPS server for LDAP Server Information. Specify the LDAPS port of 636 and check the box for Use TLS, as shown in the image:
Note: by default after versions 10.5(2)SU2 and 9.1(2)SU3 FQDN configured in LDAP Server Information is checked against the Common Name of the certificate, in case the IP address is used instead of the FQDN, the command "utils ldap config ipaddr" needs to be issued to stop the enforcement of FQDN to CN verification.
Step 2. In order to complete the configuration change to LDAPS, Click Perform Full Sync Now, as shown in the image:
Step 3. Navigate to CUCM Administration > User Management > End User and verify that end-users are present, as shown in the image:
Step 4. Navigate to ccmuser page (https://<ip address of cucm pub>/ccmuser) in order to verify that the user login is successful.
The ccmuser page for CUCM version 12.0.1 looks like this:
The user can successfully log in after LDAP credentials are entered, as shown in the image:
Configure Secure LDAP Authentication
Configure CUCM LDAP Authentication in order to utilize LDAPS TLS connection to AD on port 3269.
Navigate to CUCM Administration > System > LDAP Authentication. Type the FQDN of the LDAPS server for LDAP Server Information. Specify the LDAPS port of 3269 and check the box for Use TLS, as shown in the image:
Note: If you have Jabber clients, it is recommended to use port 3269 for LDAPS Authentication, since Jabber timeout for login can occur if a secure connection to the global catalog server is not specified.
Configure Secure Connections to AD for UC Services
If you need to secure UC services that utilize LDAP, configure these UC services to utilize port 636 or 3269 with TLS.
Navigate to CUCM administration > User Management > User Settings > UC Service. Find Directory Service that points to AD. Type the FQDN of the LDAPS server as the Host Name/IP Address. Specify the port as 636 or 3269 and protocol TLS, as shown in the image:
Note: The Jabber client machines also need to have the tomcat-trust LDAPS certificates that were installed on CUCM installed in the certificate management trust store of the Jabber client machine in order to allow the Jabber client to establish an LDAPS connection to AD.
Use this section to confirm that your configuration works properly.
In order to verify the actual LDAPS certificate/certificate chain sent from the LDAP server to CUCM for the TLS connection, export the LDAPS TLS Certificate from a CUCM packet capture. This link provides information on how to export a TLS certificate from a CUCM packet capture: How to Export TLS Certificate from CUCM Packet Capture
There is currently no specific information available to troubleshoot this configuration.