Hi, I'm having trouble with Jabber video logging in to the VCS with a AD user account. It seems in this particular case i HAVE to have NTLM enabled.
Right now only testing on the VCS Control. No firewalls in the way. Jabber video client on the inside network.
In past installs I've set the "NTLM protocol challenges" = "OFF" and I was able to have jabber login with a local account OR an AD account.
Debugs showed that both login types were using MD5 wtih local or AD user accounts.
In this case Jabber Video (4.4, 4.5 and 4.6) won't login to a AD account unless the NTLM challenge is set to ON
My setup is
TMS Version: 14.1.1 with provisioning extension 1.0.159
VCS Version: X7.2.1
Jabber Video: 4.6 (4.6.3.17194) on windows-7 64-bit
This was exactly the same as my past 2 installs but this is behaving differently.
Could there be something different on the customers AD configuration ?
Perhaps some extra security setting on the domain that would cause this to happen
I've been able leave NTLM=OFF in my past installs and was able to use both local accounts (for hardware endpoints and non-ad users) and AD accounts for Jabber provisioning.
I dont know whats different here
VCS Control Settings
- Default Zone
- Auth Policy - Check Creds
- Default Subzone -
- Auth Policy - Check Creds
- Registration - allow
- Traversal Zone- Client
- Auth Policy - Check Creds
