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

Managing Security 162
v>
-->
<ssl>false</ssl>
<ShadowPassword>false</ShadowPassword>
<CaseSensitiveUserName>false</CaseSensitiveUserName>
<!-- multiple DN entries are allowed, they will be tried one at a time -->
<DN>CN=$NAME$,OU=Engineering,DC=HP,OU=US,DC=COM</DN>
<!-- provide FullNameAttribute and EmailAttribute if full name and email
attribute
are to be synchronized between LDAP and the database -->
<FullNameAttribute>displayName</FullNameAttribute>
<EmailAttribute>mail</EmailAttribute>
</LDAP>
</LoginHandler>
When you are done with your changes, the login-handler.xml file, may
resemble the following:
<LoginHandler>
<AdminAccountName>domain\primaryuser</AdminAccountName>
<LoginHandlerClass>
com.appiq.security.server.ActiveDirectoryLoginHandler
</LoginHandlerClass>
<LoginHandlerType>ActiveDirectory</LoginHandlerType>
<ActiveDirectory>
<PrimaryServer>IP address of primary domain controller</PrimaryServer>
<SecondaryServer>IP address of secondary domain
controller</SecondaryServer>
<ssl>false</ssl>
<ShadowPassword>false</ShadowPassword>
<CaseSensitiveUserName>false</CaseSensitiveUserName>
<SearchBase>DC=MyCompanyName,DC=COM</SearchBase>
<FullNameAttribute>displayName</FullNameAttribute>
<EmailAttribute>mail</EmailAttribute>
</ActiveDirectory>
</LoginHandler>
LDAP
The LDAP server requires a distinguished name (DN) and credentials. The DN can be configured,
allowing name substitution and support for multiple DN configurations.
To configure the management server to use LDAP:
1. Before switching to LDAP authentication mode, the management server needs to be configured
with a designated LDAP user through the <AdminAccountName> tag. At startup, the
designated LDAP user is mapped to the built-in “admin” user and overrides it with the LDAP user
information.
IMPORTANT: Make sure the administrator account has already been created in LDAP
before you add it to the login-handler.xml file.
a. On the management server look in %MGR_DIST\Data\Configuration