The LDAP Authenticator can provide field values for the user record (user properties) to be used in any client application for customized solutions. In the LDAP.xml file you can specify which field corresponds to which LDAP user node attribute. The field can be either an existing field from the $Users catalog in Cumulus or you can define your own field by specifying a new unique ID for it. (To specify a new unique ID, you should use the function provided by your operating system, e.g. for Linux use the command uuidgen -t or for Mac OS X use the command uuidgen.)

In any Cumulus Internet solution, you can display the field value using the standard <cumulus:fieldValue> JSP tag with the unique ID of the field.

If the user has a record in the $Users catalog of Cumulus, the field values from this record have precedence over values from the LDAP Authenticator.

To have LDAP Authenticator providing field values you have to configure the following items of the LDAP.xml file:

The example LDAP.xml files provide one by one mappings of LDAP attribute values to Cumulus field values. The examples include those attributes included in a standard ActiveDirectory and OpenDirectory LDAP installation that have corresponding Cumulus fields in the $Users catalog. If you want your mapping to include another attribute from a user node, you have to add it as a new field element to your LDAP.xml file. If you use any LDAP scheme other than ActiveDirectory and OpenDirectory, you have to adapt the structure to the structure of your LDAP scheme and replace the pre-configured field elements by field elements fitting your LDAP scheme.