Missing DS LDAP Docu

In this section you can make some default mappings. You can override this setting in each specific mapping if you need to do. In the default configuration, there are three default mappings.

RecoderName is the most importen of all. This points to the main value of the LDAP node. By default ist the name of the node, but can as well be a different attribute of the node. Some Record Types have unusual requirements, like the RecordName of a mount record must be the url. ex: “server.domain.tld:/export/home/user” User Records

If a value is needed, which is actually not in present in the LDAP, it's not ever needed to extend the LDAP. You can map a attribute to a “fix” value in place of a LDAP attribute. If you mapping starts with a ”#”, the value of the mapping, without the ”#”, is used in place of the value of a LDAP attribute. With this trick its easy to give a set of MCXSettings to the client, which nobody realy wants on a LDAP. Variables

As an extension to the fix values, you can have variables in the string which will be extended on query time. With this trick you can build a value based on some fixparts and strings vom attributes from the LDAP. An exaple of this is AuthenticationAuthority in the Users Record. To use Kerberos authentication its may be set to ”#Kerberosv5;;$uid$;KERB.DOMAIN.TLD”. The “$uid$” is replaced with the value of the uid attribute of the LDAP node. If you use this cleverly, this is a strong tool.

Attention: Attributes are only available, if it's used in an othe mapping an therefor queried. The dscl some time query the LDAP for more attributes as its need. If it's work in dscl, it not sure to work!