04-26-2012 07:32 AM - edited 03-17-2019 02:18 PM
How can I setup our VCS to allow Cisco Jabber users to login via LDAP (username without domain), not to be confused with AD (Direct). I have both LDAP and AD (Direct) both setup and enabled in our VCS due to testing both some time ago, but I'm not sure if it's okay to run both at the same time. When I test it, I get authentication failed.
Thanks!
04-26-2012 07:43 AM
..forgot to mention that I have looked over the VCS Authentication documention, but just want to clarify on how it's done, since its not working for me.
04-26-2012 03:18 PM
In short, you have to have a proper h.350 directory reflecting the provisioning directory, LDAP as the
database type and proper zone auth settings.
To prevent Movi/Jabber to use NTLM set "NTLM protocol challenges" to "off".
That shall do the trick.
Please remember to rate helpful responses and identify
04-26-2012 06:58 PM
Maybe Movi/Jabber need to TMS provide user authentication.
I must complete TMS agent function.add user on TMS-->system-->provision-->direction.VCS can provide user's authentication.
04-26-2012 08:41 PM
Hi Patrick,
Any need for running both at same time??
Jabber can utilize AD direct or H.350 for authentication purpose. I love AD direct mechanism thats fairly simple to implement and straight forward.
For H.350 you should have all the LDAP information and schemas to be uploaded in AD.
Thanks
Alok
04-30-2012 07:15 AM
No reason, I was simply doing a test of each and never disabled them afterward. I was able to get AD working, but having the domain as part of the username would mean all of our users would need to adjust their logins, something that could be confusing and troublesome for some. That is why I was trying LDAP, from my knowledge, they wouldn't need the domain correct? I think what I'm missing is the LDAP schemeas, I'll have to ask our network administrator of the possibility about them being installed, something I didn't know of until now.
04-30-2012 12:38 PM
Hi Patrick,
Yes, thats required when you used the H.350 directory services lookup from LDAP.
check the page 15.
Thanks
Alok
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