12-10-2024 03:57 AM
Hello All,
We are trying to integrate an LDAP server (msft Active Directory) unsuccessfully so far.
I cannot see LDAP request in CUCM, however, connectivity between CUCM and LDAP is on place since i have checked that there is ping response from CUCM.
In CUCM side, there is not much to configure. I'm afraid that, in LDAP server side, I'm missing something.
Have you faced a similar issue?
Thanks,
Juan
12-10-2024 04:19 AM
You did not say if you were doing LDAP or LDAPS, so I'll assume LDAP. What is required is pretty well described in this link.
The most common issue I have seen in LDAP integrations is that the service account needs to be able to read all attributes of user objects and have a password that does not expire.
12-10-2024 04:58 AM
Maybe the ping might be enabled; however, the ports used for LDAP/LDAPS might be blocked. When checking connectivity, it's always recommended to use the port it uses instead of just pinging.
As @Elliot Dierksen mentioned, the service account is often the cause of LDAP integration failures.
12-10-2024 05:47 AM
In addition to double-checking the service account and its permissions (it has to have full read access to accounts) as mentioned by @Elliot Dierksen, the other mistake most folks make is the construction of their User Search Base. Your MS people can help you with the syntax for that.
Maren
12-10-2024 11:16 AM
@Juan Delgado Gutierrez wrote:
I cannot see LDAP request in CUCM, however, connectivity between CUCM and LDAP is on place since i have checked that there is ping response from CUCM.
What exactly do you mean by you don't see LDAP requests in CUCM? We need some more context about what you're trying to do and what you're seeing.
Quick tip, when you configure the Directory and Authentication pages, when you click "Save", CUCM connects to the IP/fqdn/port # of whatever LDAP servers you have configured to test the socket. If you go to those pages and simply click "Save", and you don't receive a connectivity failure banner at the top of the page, then your connectivity is good.
12-10-2024 11:30 AM
@Brad Magnani - I was originally going to say something similar about CUCM (and CUC) reaching out with the credentials to the User Search Base when "Save" is clicked. But my experience is that depending on the exact version of CUCM sometimes it did and sometimes it didn't. (The last time it didn't was one of the v10 revs, to be fair.)
More recently, the credentials are checked for connectivity to the LDAP database itself but the User Search Base is not verified at "Save". I've experienced this with v12.5. I haven't checked v14 or v15 yet.
Maren
12-10-2024 11:59 AM
I quickly checked on a 14.x lab and after the LDAP bindResponse comes back successfully it does send a searchRequest for the baseObject which matches what's configured in the configured LDAP User Search Base field. I configured a search base that doesn't exist out in LDAP and did the test again, and it fails since that is also being validated in addition to the TCP socket. This behavior should be consistent on 15.x as well.
12-10-2024 11:35 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