AudioCodes Mediant 800 User Manual page 264

CHAPTER 16 Services
For the device to run a search, the path to the directory's subtree, known as the distinguished
name (DN), where the search is to be done must be configured (see
(Base Paths) per LDAP
and one or more attributes whose values must be returned to the device must also be
configured. For more information on configuring these attributes and search filters, see
based Routing for Microsoft Skype for
The device can store recent LDAP queries and responses in its local cache. The cache is used
for subsequent queries and/or in case of LDAP server failure. For more information, see
Configuring the Device's LDAP
If connection with the LDAP server disconnects (broken), the device sends the SNMP alarm,
acLDAPLostConnection. Upon successful reconnection, the alarm clears. If connection with
the LDAP server is disrupted during the search, all search requests are dropped and an alarm
indicating a failed status is sent to client applications.
■ Management-related LDAP Queries: LDAP can be used for authenticating and authorizing
management users (Web and CLI) and is based on the user's login username and password
(credentials) when attempting login to one of the device's management platforms. When
configuring the login username (LDAP Bind DN) and password (LDAP Password) to send to
the LDAP server, you can use templates based on the dollar ($) sign, which the device
replaces with the actual username and password entered by the user during the login attempt.
You can also configure the device to send the username and password in clear-text format or
encrypted using TLS (SSL).
The device connects to the LDAP server (i.e., an LDAP session is created) only when a login
attempt occurs. The LDAP Bind operation establishes the authentication of the user based on
the username-password combination. The server typically checks the password against the
userPassword attribute in the named entry. A successful Bind operation indicates that the
username-password combination is correct; a failed Bind operation indicates that the
username-password combination is incorrect.
Once the user is successfully authenticated, the established LDAP session may be used for
further LDAP queries to determine the user's management access level and privileges
(Operator, Admin, or Security Admin). This is known as the user authorization stage. To
determine the access level, the device searches the LDAP directory for groups of which the
user is a member, for example:
CN=\# Support Dept,OU=R&D
Groups,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC=com
CN=\#AllCellular,OU=Groups,OU=APC,OU=Japan,OU=ABC,DC=corp,DC=abc,DC
=com
The device then assigns the user the access level configured for that group (in
Access Level per Management Groups
to search for the user's member group(s) is configured using the following:
● Search base object (distinguished name or DN, e.g.,
"ou=ABC,dc=corp,dc=abc,dc=com"), which defines the location in the directory from
where the LDAP search begins and is configured in
per LDAP
● Search filter, for example, (&(objectClass=person)(sAMAccountName=JohnD)), which
filters the search in the subtree to include only the specific username. The search filter can
be configured with the dollar ($) sign to represent the username, for example,
(sAMAccountName=$). To configure the search filter, see
Filter
● Management attribute (e.g., memberOf), from where objects that match the search filter
criteria are returned. This shows the user's member groups. The attribute is configured in
the LDAP Servers table (see
Server). The search key (filter), which defines the exact DN to search
Cache.
Server.
Attribute.
Configuring LDAP
Mediant 800 Gateway & E-SBC | User's Manual
Business.
Attributes). The location in the directory where you want
Configuring LDAP DNs (Base Paths)
Servers).
- 224 -
Configuring LDAP DNs
AD-
Configuring
Configuring the LDAP Search