Starter Pack - Cisco TelePresence Administrator's Manual

Note that the same credentials can be used by more than one endpoint - you do not need to have a separate
entry in the database for each endpoint.
Credentials managed within TMS (for device provisioning)
The local database includes any credentials supplied by TMS, in addition to any entries that have been added
manually.
Incorporating TMS credentials within the local database aids migration from a provisioning-only authenticated
system to a configuration where all messages are authenticated. It means that VCS can authenticate all
messages against the credentials generated by TMS which were previously used by the Provisioning Server
just to authenticate provisioning requests (i.e. no change of password is required for provisioned devices).
TMS Provisioning Extension mode
When the VCS is using the
service are stored in the local authentication database, along with any manually configured entries. The
Source column identifies whether the user account name is provided by TMS, or is a Local entry. Only
Local entries can be edited.
TMS Agent legacy mode
The credentials supplied by the TMS Agent are stored in a separate TMS Agent database. The VCS checks
credentials by looking in both the local authentication database and the TMS Agent database.
(Prior to X7.0, the VCS did not check against the TMS Agent database, it only checked the manually
configured credentials in the local database.)
Using the local database with other authentication mechanisms
Local database authentication in combination with H.350 directory authentication
From version X7.2, you can configure the VCS to use both the local database and an H.350 directory.
If an H.350 directory is configured, the VCS will always attempt to verify any Digest credentials presented
n
to it by first checking against the local database before checking against the H.350 directory.
(Prior to version X7.2, the VCS could be configured to verify credentials against either the local database or
an H.350 directory service.)
Local database authentication in combination with Active Directory (direct) authentication
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.
NTLM challenges are offered in addition to the standard Digest challenge.
n
Endpoints that support NTLM will respond to the NTLM challenge in preference to the Digest challenge,
n
and the VCS will attempt to authenticate that NTLM response.

Starter Pack

If the Starter Pack option key is installed, the local authentication database will include a pre-configured set
of authentication credentials. To ensure correct operation of the TURN server in conjunction with the Starter
Pack, do not delete or modify the StarterPackTURNUser entry in the local authentication database.
Cisco VCS Administrator Guide (X7.2)
TMS Provisioning Extension services, the credentials supplied by the Users
Device authentication
Page 113 of 498