02-08-2016 09:57 AM - edited 03-19-2019 10:42 AM
We are upgrading from 8.6 to 10.5. Ldap synchronization and authentication are enabled. LDAP Syncronization works just ine. LDAP Authentication works fine on 8.6 Call Manager, but fails on 10.5. The configuration in 10.5 mirrors the configuration in 8.6
For example, I can log in using a network credential to my 8.6 CM Administration Page, however using the same network credential on 10.5 authentication page it fails.
My network credential is sync'd in Call Manager. I have assigned myself every possible permission call manager offers.
What am I missing?
02-08-2016 10:17 AM
What LDAP are you integrating to?
02-08-2016 10:35 AM
Microsoft Active Directory.
02-08-2016 10:36 AM
02-08-2016 10:44 AM
What version??
And did you have a secure LDAP integration???
Or using wildcard certs on 8.6??
02-08-2016 10:54 AM
Which version of Active Directory? 6.1
I took a look in Cert Managment, looks like they are not self signed.
02-08-2016 03:05 PM
do you get any error?
is the Cisco dirsync service activated, try restarting the dirsync service and see if it works.
there could also be an issue with the wrong search-base entered.
02-09-2016 07:18 AM
02-09-2016 10:22 AM
Are you using TLS and/or wildcard certs??
02-11-2016 01:38 PM
Figured out the issue. Needed the FQDN versus IP address in the LDAP authenticaion configuration.
02-11-2016 01:37 PM
Figured out what the issue was. 10.5 was expecting the FQDN versus the IP address of the LDAP Servers.
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