3PAR InForm® OS 2.3.1 Concepts Guide (320-200112 Rev B, February 2010)

4.2
Overview
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1
there are multiple InServ servers configured to use the same LDAP server in the same way, a
single user with access to one InServ server can access all of the environment’s InServ servers
with the same privileges.
Accessing objects on InServ servers configured to use 3PAR Virtual Domains requires privileges
in the domain in which those objects reside. The configuration of domains may differ from one
InServ system installation to the next. This results in differing levels of privileges over objects
based on mapping between the LDAP configuration and the individual InServ server’s domain
configuration.
The InForm OS LDAP client is designed to work with various LDAP servers and schemas for data
organization. However, only use with the Active Directory LDAP directory implementation is
currently supported.
Configuring the InForm OS to use LDAP can only be performed with the 3PAR InForm
Command Line Interface (CLI). Refer to the 3PAR InForm OS CLI Administrator’s Manual for
instructions on how to perform these tasks.
4.1.1 Active Directory
Active Directory is an implementation of LDAP directory services by Microsoft for use in
Windows environments. An Active Directory server is both an LDAP and Kerberos server. When
set up for SASL binding (see SASL Binding on page 4.6), the Active Directory server and
Kerberos server are used for both authorization and authentication of users.
NOTE: At the current time, the OpenLDAP directory implementation is also
available, however, on a limited basis. Check with your local 3PAR service
representative for updates on availability.
NOTE: All LDAP related tasks are performed with the 3PAR InForm Command
Line Interface (CLI).