you could authenticate your Movi/Jabber Users against AD with Kerberos and NTLM. Therefore the VCS must join the AD Domain as a Computer. You can do this under VCS Configuration -> Authentication -> Devices -> Active Directory Service. After joining the Jabber Users can be authenticated with AD.
Have you got TMS? With TMS you can sync your AD Users to the TMS and from the TMS to the VCS. You could also filter for a special AD group.
NTLM Auth works only for Jabber Clients, so you have to maintain a separeate database for all your other endpoints. You can maintain this database directly on the VCS.
A H.350 LDAP database could also be used to maintain the credentials, but you have to build a seperate directory. I like the TMS because it's easy to manage. On the other hand, if you have multiple VCS or the VCS clustered, a single database would be better.
I'm not quite sure, but I think with TMSPE you could also use the Provisioning database to maintain the credentials for all your endpoints. TMSPE syncs the accounts to the VCS database, so authentication should work fine with them too.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...