Configure Cucm For Secure Ldap Directory
Configure Cucm For Secure Ldap Directory
Contents
Introduction
Prerequisites
Requirements
Components Used
Background Information
Verify and Install LDAPS Certificates
Configure Secure LDAP Directory
Configure Secure LDAP Authentication
Configure Secure Connections to AD for UC Services
Verify
Troubleshoot
Related Information
Introduction
This document describes the procedure to update CUCM connections to AD from a non-secure LDAP
connection to a secure LDAPS connection.
Prerequisites
Requirements
• AD LDAP Server
• CUCM LDAP Configuration
Components Used
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.
Background Information
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.
Note: See this link for information in order to update from non-secure LDAP to secure LDAPS
connections to AD for other Cisco Collaboration Applications: Software Advisory: Secure LDAP
Mandatory for Active Directory Connections
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):
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 are 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 is 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 log in 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:
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 log in 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.
Verify
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
Troubleshoot
There is currently no specific information available to troubleshoot this configuration.
Related Information
• This link provides access to a video that walks through the LDAPS configurations: Secure LDAP
Directory and Authentication Walkthrough Video
• Technical Support & Documentation - Cisco Systems