Alias Origin; Ldap; Combined; Endpoint - TANDBERG Video Communication Server Administrator's Manual

Grey Headline (continued)
Registration control
Configuring LDAP server settings
The LDAP Configuration page allows you to configure a connection to the LDAP database to be used
during authentication.
To go to the LDAP Configuration page:
• VCS configuration > Authentication > LDAP > Configuration.
To configure these settings using the CLI:
• xConfiguration LDA P
• xConfiguration Authentication LDA
LDAP server
The IP address or FQDN (or server address, if a DNS
LDAP server.
Port
The IP port of the LDAP server.
The default is 389.
Encryption
Determines whether the connection to the LDAP server will be encrypted. (For more information on
configuring encryption, see Securing the LDAP connection with
TLS: TLS Encryption will be used for the connection with the LDAP server.
Off: No encryption will be used.
The default is Off.
UserDN
The user distinguished name to be used by the VCS when binding to the LDAP server.
Password
The password to be used by the VCS when binding to the LDAP server.
Base DN
The area of the directory on the LDAP server to be searched for the credential information.
This should be specified as the Distinguished Name (DN) in the LDAP directory under which the
H.350 objects reside.
Overview and
Introduction Getting started
status
D14049.05
February 2009
Authentication using LDAP
P
Domain Name has also been configured) of the
TLS.)
System VCS
configuration configuration

Alias origin

This setting determines the alias(es) with which the endpoint will attempt to register. The options
are as follows:

LDAP

The alias(es) presented by the endpoint will be used as long as they are listed in the LDAP database
for the endpoint's username.
•
If an endpoint presents an alias that is listed in the LDAP database, it will be registered with that
alias.
•
If more than one alias is listed in the LDAP database for that username, the endpoint will be
registered with only those aliases that it has presented.
•
If an endpoint presents an alias that is not in the LDAP database, it will not be registered with
that alias.
•
If an endpoint presents more than one alias but none are listed in the LDAP database, it will not
be allowed to register.
•
If no aliases are presented by the endpoint, it will be registered with all the aliases listed in the
LDAP database for its username. (This is to allow for MCUs which additively register aliases
for conferences, for example the TANDBERG MPS (J4.0 and later) which registers ad-hoc
conferences.) (This applies to H.323 only).
•
If no aliases are listed in the LDAP database for the endpoint's username, then the endpoint will
be registered with all the aliases it presented.

Combined

The alias(es) presented by the endpoint will be used in addition to any that are listed in the LDAP
database for the endpoint's username. In other words, this is the same as for LDAP, with one
exception:
•
If an endpoint presents an alias that is not in the LDAP database, it will be allowed to register
with that alias.

Endpoint

The alias(es) presented by the endpoint will be used; any in the LDAP database will be ignored.
•
If no aliases are presented by the endpoint, it will not be allowed to register.
The default is LDAP.
Zones and Call Bandwidth
neighbors processing control
67
TANDBERG VIDEO COMMUNICATIONS SERVER
Firewall
Applications Maintenance
traversal
ADMINISTRATOR GUIDE
Appendices