IBM BladeCenter Management Module, Руководство пользователя

Страница: 50 / 78

Client authentication . A bind attempt is made with the client
distinguished name and password specified by this configuration
parameter. If the bind is successful, the user authentication phase
proceeds as in Anonymous authentication.
User Principal Name . A bind attempt is made directly with the
credentials used during the login process. If this succeeds, the user has
passed the user authentication phase. The user principal name usually
refers to a fully qualified name, such as johndoe@abc.com. However,
johndoe would also be acceptable.
Strict User Principal Name . This is similar to the user principal name,
except that a fully qualified name must be entered by the user. That is,
johndoe@abc.com would be acceptable, but not johndoe. The name
entered by the user will be parsed for the @ symbol.
Configuring the LDAP client authentication
Complete the following steps to configure the LDAP client authentication:
1. In the navigation pane, click MM Control
→
Network Protocols .
2. Scroll down to the Lightweight Directory Access Protocol (LDAP) Client
section and click Set DN and password for Client Authentication . A page
similar to the one in the following illustration is displayed.
3. The initial bind to the LDAP server during user authentication can be performed
with anonymous authentication, client-based authentication, or user principle
name. To use client-based authentication, in the Client DN field, type a client
distinguished name. Type a password in the Password field or leave it blank.
Configuring the LDAP search attributes
Complete the following steps to configure the LDAP search attributes:
1. In the navigation pane, click MM Control
→
Network Protocols .
2. Scroll down to the Lightweight Directory Access Protocol (LDAP) Client section
and click Set search attribute names for LDAP based authentication . A page
similar to the one in the following illustration is displayed.
40
BladeCenter Management Module: User’s Guide