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

nisLDAPobjectDN hosts: \ou=hosts,?one?, \objectClass=device, \objectClass=ipHostTo:nisLDAPobjectDN hosts: \ou=newHosts,?one?, \objectClass=device, \objectClass=ipHostThis change causes entries to be mapped underdn: ou=newHosts, dom=domain1, dc=sun, dc=cominstead of underdn: ou=hosts, dom=domain1, dc=sun, dc=com.Example 2–Implementing a Custom MapThis example shows how to implement a custom map.A hypothetical map, servdate.bynumber, contains information about the servicing datesfor systems. This map is indexed by the machine’s serial number which, in thisexample, is 123. Each entry consists of the machine owner’s name, a colon, and acomma-separated list of service dates, such as John Smith:1/3/2001,4/5/2003.The old map structure is to be mapped onto LDAP entries of the following form:dn: number=123,ou=servdates,dc=... \number: 123 \userName: John Smith \date: 1/3/2001 \date: 4/5/2003 \...objectClass: servDatesBy examining the NISLDAPmapping file, you can see that the mapping closest to therequired pattern is group. The custom mappings can be modeled on the groupmapping. Since there is only one map, no nisLDAPdatabaseIdMapping attribute isrequired. The attributes to be added to NISLDAPmapping are the following:nisLDAPentryTtl servdate.bynumber:1800:5400:3600nisLDAPnameFields servdate.bynumber: \("%s:%s", uname, dates)nisLDAPobjectDN servdate.bynumber: \240 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005