cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
203
Views
4
Helpful
4
Replies

Cucm Ldap authentication error

s.maxina1
Level 1
Level 1

Hi all

i have a cucm 10.5.1 and ldap authentication work perfectly until today. When i ask system admin about Active Directory, he told me about change password policies in recent days. So we need to reset the password again for related user. It is regarded that when i ran “perform full sync now”, I encountered this error: “ login failure to host …., please re-enter ldap manager distinguished name and password “

but, after sys admin set new password, this error is shown:

error while connecting to ldap… , null

It is regarded that, we can login to any windows machine with this user without problem and has as same as previous access level.

Why?

best regards

4 Replies 4

wasosa
Level 1
Level 1

In addition to the ‘new password policy change“, do they now require you to connect via Secure LDAP (LDAPS) instead of just LDAP? If so, you might have to change the default port (and maybe new cert) for new secured connection.

By the way, have you tried deleting the LDAP configuration profile and recreate it from scratch in CUCM? You might want to check the logs for additional details about the error.

No. Its still working on ldap. In system, ldap authentication there is no profile to delete and create it again. How to find related logs in cucm( in rtmt which section will show related logs?)

It would be Directory synchronisation logs.



Response Signature


After reproducing the error, pull the following from RTMT:

Cisco Tomcat 
Cisco Tomcat Security
Cisco DirSync
EventViewer-Application Logs
EventViewer-SystemLogs

First check in the Tomcat Security logs (most often will contain socket exceptions or context failure codes returned from LDAP).  If those don't point to anything helpful, you can run a packet capture on the publisher while you save the page.  When you save it, it tries connecting to the configured LDAP server with whatever configuration settings you have enabled and if it's something TCP socket related, you will often see more details there vs. in the logs.

Brad