The Build subsection contains a list of LDAP attributes and the definitions of their values. It must contain at least all mandatory attributes for an object class, and the DN. If the DN definition is missing from the Build section, the entries cannot be created in the directory.
You do not need to specify a DN definition in the Build sections of the radius.mapping file because this file is not used to import entries into the directory.
Attribute value definitions can be made up of:
A variable or keyword specified in any of the sections of the table definition
A configuration variable specified in the Common section that applies to all the tables in the Front-End section
A constant expression
A concatenation of any of the above
The syntax of an LDAP attribute and its associated value definition in the Build section is as follows:
LDAPattribute=attributeValueDefinition |
For example, if you wanted to create an entry for a mail alias, and use the LDAP attribute rfc822mailMember to store the names of alias members, your mapping would contain the following definitions:
Condense: aliasMember=string2instances($aliasList, ",") trimAliasMember=trim($aliasMember) ... Build: rfc822mailMember=$trimAliasMember ... |