Naming and Directory Services (DNS, NIS, and LDAP)

Attribute MapThe Solaris LDAP naming service allows one or more attribute names to be remappedfor any of its services. (The Solaris LDAP client uses the well-known attributesdocumented in Chapter 14.) If you map an attribute, you must be sure that theattribute has the same meaning and syntax as the original attribute. Note thatmapping the userPassword attribute might cause problems.There are a couple of reasons you might want to use schema mappings.■■You want to map attributes in an existing directory serverIf you have user names that differ only in case, you must map the uid attribute,which ignores case, to an attribute that does not ignore caseThe format for this attribute isservice:attribute-name=mapped-attribute-name.If you want to map more than one attribute for a given service, you can definemultiple attributeMap attributes.In the following example, the employeeName and home attributes would be usedwhenever the uid and homeDirectory attributes would be used for the passwdservice.attributeMap: passwd:uid=employeeNameattributeMap: passwd:homeDirectory=homeThere exists one special case where you can map the passwd service’s gecos attributeto several attributes. The following is an example.attributemap: gecos=cn sn titleThis maps the gecos values to a space separated list of the cn, sn, and titleattribute values.objectClass MapThe Solaris LDAP naming service allows object classes to be remapped for any of itsservices. If you want to map more than one object class for a given service, you candefine multiple objectclassMap attributes. In the following example, themyUnixAccount object class is used whenever the posixAccount object class isused.objectclassMap: passwd:posixAccount=myUnixAccount136 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005