...
Connecting to LDAP Over SSL
| Include+ | ||||
|---|---|---|---|---|
| ||||
| Include Page | ||||
|
Configuring Directory Settings
| Anchor | ||||
|---|---|---|---|---|
|
...
| Base DN | The base DN is the context DN (distinguished name) where the directory objects reside. If empty, User Administration will use the root DN of the directory tree. Organizational units (ou) and domain components (dc) are used to define directory tree structures. The following example shows how an organization could structure its directory:
In this example, you would enter the following base DNs to scan users from Europe and Asia only.
| |||||
|---|---|---|---|---|---|---|
| Filter | Enter an expression in the Filter field to search on specific parameters. Searches are performed on the base DN(s) and specified scope. The following examples describe some of the ways filters can be used: Simple filter for users under provided base DN:
Find "devel1" and "devel2" users only:
Find users that are members of group "Managers":
| |||||
| Restrict To Groups | Enable this option to import only the users that belong to a group specified in the Group Import Settings. Users that do not belong to a group configured in Group Import Settings will not be imported. | |||||
Attribute Mappings The attributes mapping section defines how User Administration attributes (i.e., user login name, first name, last name, and email) map to directory object attributes (i.e., uid, givenName, sn, and email). You can use the defaults mappings or configure the attributes to align with your LDAP server. Refer to the documentation for your LDAP server | ||||||
| Username | This field is used for the login name in DTP. The the Default is | |||||
| First Name | This field is used for the the users' first name in DTP. The Default is | |||||
| Last Name | This field is used for the users' last name (surname) in DTP. The | |||||
| Email Address | This field is used for the users' email address in DTP. The | |||||
| Member Of | This field is used to associate users in DTP with LDAP groups. Default is | |||||
...
| Enable group import | If you want to import groups set in your LDAP, enable the Enable Group Import option. | |||||
|---|---|---|---|---|---|---|
| Base DN | See the Base DN setting under User Import Settings. | |||||
| Filter | See the Filter setting under User Import Settings.
| |||||
| Enable nested groups | If groups contain other groups in your directory, you can enable this setting to retain your LDAP server's hierarchical structure. | |||||
| Ancestor groups only | A nested group may contain users, in addition to other groups. An ancestor is a user that is the immediate member of a group nested inside another group. In the following example, MEMBER B and C are the ancestors within the groups nested within GROUP A.
You can enable the Ancestor groups only option and specify a group name in the Ancestor group names field to import only the immediate members associated with the nested groups. Members of the group specified in the Ancestor group names field will also be imported.
| |||||
| Ancestor group names | If the Ancestor groups option is enabled, specify the name of the nested group that contains the ancestors you want to import. | |||||
Attribute Mappings The attributes mapping section defines how Parasoft User Administration object attributes map to the connected directory object attributes. You can use the defaults mappings or configure the attributes to meet your specific needs. | ||||||
| Name | Default is cn. | |||||
| Description | Default is cn. | |||||
| Member | Default is member. See Advanced Settings for additional information. | |||||
...