This handler will use the server information and user credentials configured in the task info values to authenticate and connect to the specified Active Directory server (using LDAP) and create a user entry.
In order to build up the Distinguished Name (a unique identifier for the active directory user entry), the handler uses a template specified as a task info value.
The following entry attributes are set once the user entry is created:
Direct Mappings
- givenname => First Name
- sn => Last Name
- displayname => Full Name
- description => Description
- physicaldeliveryofficename => Office
- telephonenumber => Telephone
- mail => Email
- title => Title
- department => Department
- company => Company
Computed Mappings
- userprincipalname => Is set the the "User Logon" parameter if it was provided using the User Principal Name format. This attribute is not set if the "User Logon" parameter was provided without the "@domain" suffix.
- samaccountname => Is set to the username portion of the "User Logon" parameter.
- initials => A concatenated string of the capitalized first letters of each word in the "Full Name" parameter.
Special Attributes
- objectclass => [top,person,organizationalPerson,user]
If the node parameter "Activated" is set to 'Yes', the user will be activated immediately after the entry attributes have been set.
Task Info Configuration
- dn_format - This value is used to specify the distinguished name of the Active Directory user entry to be created. Anything within curly braces {} will be replaced with the value of the entry attribute or task info value associated with that key. For example, the default format is 'CN={displayname},CN=Users,{base}'. In this case {displayname} is replaced with the displayname attribute value and {base} is replaced with the value of the 'base' task info value. A full list of available entry attributes is available above. If you use organizational units they can be substituted into the distinguished name in this manner.
