Showing results for 
Search instead for 
Did you mean: 

Unable to sign in to CM Attendant Console, CCMUser pages: LDAP error


We recently updated from to Once we finished updating, users are no longer to sign in to the CCMUser portal. Users who use the CM Attendant Console are also unable to sign in. We were able to sign-in appropriately prior to the upgrade. On the CCMUser portal, I am getting the following error:

'An LDAP Error has occurred. Retry the username and password. Contact your system administrator if the problem persists.'


I have made sure that the users who need it are assigned the Standard CCM User Role. I have also removed that role from my account, saved, then added it back and saved. No change.

Oddly enough, I can go into System-->LDAP-->LDAP Directory, perform a sync and it will pull in new users or remove users accordingly.

We use secure LDAP for Microsoft AD. All certificates are loaded to the system.


Any help would be much appreciated.



1 Accepted Solution

Accepted Solutions

Then we need to check the logs, please collected "Cisco Tomcat Security Logs" through RTMT covering the time of a login attempt.

View solution in original post

7 Replies 7

Shadi Shami
Rising star
Rising star

Hello Kevin,


To isolate the issue, can you please create local user with Standard CCM User Role and test it?


Thank you,


a local user works fine. Test user is able to sign in to the CCMUser portal with no issue.

Which means only active directory users affected.

We need to confirm if both LDAP sync and LDAP Authentication configured properly, can you please navigate into each one and hit click on save. And please confirm the configurations are correct.


1. system > LDAP > LDAP Directory: Click on save.

2. system > LDAP> LDAP Authentication: Click on save

Yes, these have been confirmed working.

Then we need to check the logs, please collected "Cisco Tomcat Security Logs" through RTMT covering the time of a login attempt.

In looking through the Tomcat Security Logs, it kept erroring out due to a FQDN/hostname mismatch in the certificate. I verified it as correct in the certificate. For the time being, after talking to TAC, we issued a 'utils ldap config ipaddr' to match on IP instead of FQDN. We'll revisit the security certificate issue at a later date when users won't be impacted by testing. Thanks for the nudge in the right direction.

Thanks for the update.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: