HP Storage Essentials NAS Manager Software - Manual (Page 196)

Managing Security 164
The login-handler.xml file contains two sets of tags: one for
Active Directory and one for LDAP. Make sure you change the value of the
tags that are children of the tags.
8. Provide the LDAP search base in which you want the management server to look up AD/LDAP
user attributes. Allow no spaces between commas and put in all components of fully qualified
domain name, for example, hds.usa.com would be DC=hds,DC=usa,DC=com.
The search base is used to specify the starting point for the search. It
points to a distinguished name of an entry in the directory hierarchy.
CN=$NAME$,dc=MyCompanyName,dc=COM
or:
CN=$NAME$,OU=NetworkAdministration,
dc=MyCompanyName,ou=US,dc=COM
The management server searches only those users in the company who are part of the
NetworkAdministration organization (OU=NetworkAdministration) and in the United States
(ou=US).
IMPORTANT: Different LDAP implementations may be using different keynames for CN.
The appropriate key should be mentioned in login-handler.xml. Refer to the
documentation for your LDAP server to determine how to obtain the appropriate keyname.
Your keyname may start with uid instead of CN, for example,:
uid=$NAME$,ou=,
dc=windows,dc=hp,dc=com
9. Save the login-handler.xml file.
The following is an example of a modified login-handler.xml file for use with an LDAP
server. Underlined text is information that was modified:
domain\admin
IP address of Primary Domain
Controller
IP Address of Secondary Domain Controller
false
false
false
DC=domain extension1,DC=domain extension2,DC=COM
displayName
mail