110 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
Users that are authenticated by an LDAP server can log in to the management GUI and the 
CLI. These users do not need to be configured locally for CLI access, nor do they need an 
SSH key configured to log in by using the CLI.
If multiple LDAP servers are available, you can configure more than one LDAP server to 
improve resiliency. Authentication requests are processed by those LDAP servers that are 
marked as preferred unless the connection fails or a user is not found. Requests are 
distributed across all preferred servers for load balancing in a round-robin fashion.
If users that are part of a group on the LDAP server are to be authenticated remotely, a user 
group with an identical name must exist on the system. The user group name is 
case-sensitive. The user group must also be enabled for remote authentication on the system.
A user who is authenticated remotely is granted permissions according to the role that is 
assigned to the user group of which the user is a member.
To configure remote authentication using LDAP, start by enabling remote authentication:
1. Click Settings → Security, and select Remote Authentication and then, Configure 
Remote Authentication, as shown in Figure 4-25.
Figure 4-25   Configuring remote authentication
2. Enter the LDAP settings. These settings are not server-specific. They are applied to all 
LDAP servers configured in the system. Extra optional settings are available by clicking 
Advanced Settings. The following settings are available:
– LDAP type:
 IBM Tivoli Directory Server (for IBM Security Directory Server)
 Microsoft Active Directory
Other (for OpenLDAP)
In this example, we configure an OpenLDAP server, as shown in Figure 4-26 on 
page 111.
Note: All LDAP servers that are configured within the same system must be of the same 
type.