Loading LDAP modification data

With the next action, the data structure used to add the user account is prepared. This data structure contains a number of attributes, each with one or more values. The exact attributes used to add a user account vary for each directory service implementation that supports LDAP.

Figure 18: Load LDAP modification data script action.

The resulting data structure is stored in a variable. In this example, the default variable name %LdapData% is used to store the structure. The variable is used in subsequent script actions.

According to the Novell eDirectory schema documentation, a user account must have the following attributes defined:

1. objectClass: This attribute must get 3 values, top, person and inetOrgPerson to make the new object a user account.
2. cn (Common Name): The common name is the unique identifier of the object in the directory service.
3. sn (Surname): The surname attribute must have a text value, representing the last name of the user account.

The common name is defined in the next action (Add directory service object (LDAP)). The objectClass and sn attribute are initialized in the modification data structure. Besides these attribute, also the givenName, homePhone and userPassword attributes are setup.

Figure 19: Properties of action to setup LDAP modification data.

Depending on the schema definition, an attributes can have a single or multiple values. Values can be specified using variables. In the example shown, the attributes sn, givenName and homePhone are specified using variables %SurName%, %GivenName% and %HomePhone% and linked to the input csv file. The objectClass attribute gets the same 3 values for each user account: top, person and inetOrgPerson as defined by the eDirectory schema.

To setup an individual attribute, double click one of the attributes.

Figure 20: Dialog used to specify the modification type and values of a single attribute.