Using Active Directory Database (Direct) - Cisco TelePresence Administrator's Manual

Device authentication

Using Active Directory database (direct)

Active Directory database (direct) authentication uses NTLM protocol challenges and authenticates
credentials via direct access to an Active Directory server using a Kerberos connection.
It can be enabled at the same time as local database and H.350 directory service authentication. This is
because NTLM authentication is only supported by certain endpoints. Therefore, for example, you could use
the Active Directory (direct) server method for Jabber Video, and the local database or H.350 directory
service authentication for the other devices that do not support NTLM.
If Active Directory (direct) authentication has been configured and NTLM protocol challenges is set to
Auto, then NTLM authentication challenges are offered to those devices that support NTLM. Devices that do
not support NTLM will continue to receive a standard Digest challenge.
Note that the VCS embeds NTLMv2 authentication protocol messages within standard SIP messages when
communicating with endpoint devices, and uses a secure RPC channel when communicating with the AD
Domain Controller. Users' Windows domain credentials and the AD domain administrator credentials are not
stored on the VCS.
Configuration prerequisites
Active Directory
A username and password of an AD user account with either "account operator" or "administrator" access
n
rights must be available for the VCS to use for joining and leaving the domain.
Entries must exist in the Active Directory server for all devices that are to be authenticated through this
n
method. Each entry must have an associated password.
The device entries (in all domains) must be accessible by the user account that is used by VCS to join the
n
domain. If the VCS is in a domain that is part of a forest, and there is trust between domains in the forest,
the VCS can authenticate device entries from different domains providing the user account has appropriate
rights to authenticate devices against the other domains.
Kerberos Key Distribution Center
The KDC (Kerberos Key Distribution Center) server must be synchronized to a time server.
DNS server
If a DNS name or DNS SRV name is used to identify the AD servers, a DNS server must be configured with
the relevant details. (Note that the VCS must be configured to use a DNS server even if you are not using
DNS / DNS SRV to specify the AD servers.)
VCS
The VCS must be configured to use a DNS server
n
The VCS's System host name
l
(Microsoft NetBIOS names are capped at 15 characters.)
When part of a cluster, ensure that each VCS peer has a unique System host name.
l
Ensure that an NTP server
n
If the connection is going to use TLS encryption, a valid CA certificate, private key and server certificate
n
must be uploaded to the VCS.
The VCS must be configured to challenge for authentication on the relevant zones and subzones:
n
Cisco VCS Administrator Guide (X8.1.1)
(System >
(System > DNS) must be 15 or fewer characters long.
(System > Time) has been configured and is active.
About device authentication
DNS).
Page 123 of 507