3.2

Setting User Authentication Providers and Importing Users
118
User Name Attribute Attribute that stores the user name to use for LDAP-authenticated logins. The
content of this attribute becomes the imported user name in Interplay and
defines the user name for LDAP-authenticated login attempts. This attribute
might vary according to the LDAP schema, and there might be multiple
attributes storing different varieties of the user name. For Microsoft Active
Directory LDAP and OpenLDAP, the most standard attribute is “cn,” the
common name as defined in RFC 4519. Other attributes such as displayName
or mailNickname (in an Exchange-enabled environment) might also exist.
User DN Suffix Suffix that must be appended to the user name to form a valid Distinguished
User Name (DN). The resulting DN will be used whenever a user tries to
authenticate through LDAP: Interplay will issue a simple ldap_bind request to
the directory service, using a DN constructed according to the rule given
above, and the clear text password as given by the user.
For example, if the user name specified during login is “journalist” and the
User DN Suffix is “CN=Users,DC=company,DC=com,” Interplay will try to
bind to the LDAP service using a DN of
“CN=journalist,CN=Users,DC=company,DC=com.” Access will be granted if
the bind request is allowed by the LDAP service. Depending on the LDAP
service implementation, there might be other possible ways of constructing a
DN valid for binding to the LDAP service. In Active Directory LDAP, for
example, a DN suffix of “@company.com,” resulting in a DN of
“[e-mail]” might also work.
For an example of authenticating users from an Active Directory structure
with multiple domains, see “Authentication from an Active Directory that
Includes Multiple Domains” on page 120
.
Setting Description