Configuring Vision2 For Use With Ldap; User Access Control - AMX Vision 2 Operation/Reference Manual

Configuring Vision
If you intend to use Lightweight Directory Access Protocol (LDAP), then before you begin there is an XML
file on the Vision
C:\Inetpub\wwwroot\v2Services\App_Code directory. The contents of this file are used to impersonate the
specified user when communicating with the LDAP server. For this reason, the user defined by these settings
must have read rights on the LDAP server. The file contains the following entries:



It also contains and entry for userattributecontainingloginname. This entry, as the name suggests, contains the
name of the attribute within the user Distinguished Name (DN) which holds the value that the user supplies
when they log in. For a normal Active Directory implementation, this value is sAMAccountName and for
ADAM it is usually name.

User Access Control

This section of the v2ServicesManager controls whether the system supports User Access Control (UAC), and
if so, the type of UAC employed. (Where possible, example values are provided for both Active Directory and
ADAM).
FIG. 62 User Access Control screen
2
Vision Operation/Reference Guide
2
for use with LDAP
2
server which must be edited manually. You must edit the ldsl.xml file located in the
username - This is the user to impersonate
domain - The domain in which the LDAP server resides
password - The password of the user to impersonate
Master Service
63