This section provides information on deployment time configurations.
There's a set of configuration parameters that affect the LDAP-based Identity Manager behavior. They're are described below. Keep in mind that they can be changed programatically as well, see this page for more information on the subject. The configurations parameters are managed by the ConfigurationUtils API. To know how to access the parameters on Linux and Windows systems check this page.
The following table summarizes the configurations parameters.
| Parameter name | Description |
| BulkParameterAttributeName | The name of the LDAP attribute that will store the bulk parameters. |
| LDAPUtilsImplementation | The underlying LDAP technology that should be used to access the LDAP server. |
The LDAPUtilsImplementation field may have several different values. The following table summarizes the possibilities. Note that you should use lower-case.
| Value | Description | Remarks |
| ad | The Microsoft Active Directory technology | - |
| open_ldap | The OpenLDAP technology | - |
| oid | The Oracle OID technology | Not supported at the time of this writing (Oct/08). |
As you might have read here (Additional attributes subsection) there's a kind of user attributes that might be persisted on the LDAP server. These mappings can be defined explicitly by creating a configuration key/value pair that has the business parameter name as the key and the LDAP attribute name as the value. Here's a couple of examples:
employeeID=physicalDeliveryOfficeName aBusinessParameterName=businessCategory anotherBusinessParameterName=employeeType
Check this page for the details on how to set the key/value configuration pairs on your platform.