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

Assuming the defaultSearchBase value is dc=some,dc=domain, thecorresponding LDAP entry, as listed by ldapsearch(1), would be the following.dn: cn=nisd,ou=Ppc,dc=some,dc=domaincn: nisdcn: rpc.nsidcn: nisplusdoncRpcNumber: 100300description: NIS+ serverobjectClass: oncRpcThis makes for a simple one-to-one mapping between NIS+ and LDAP data, and thecorresponding mapping attribute value going from NIS+ to LDAP is the following.nisplusLDAPattributeFromColumn \rpc: dn=("cn=%s,", name), \cn=cname, \cn=name, \oncRpcNumber=number, \description=commentThis constructs the DN for the entry to be cn=%s, with the value of the cname columnsubstituted for %s.cn=nisd,Since the value ends in a comma, the read base value from the nisplusObjectDN isappended, and you have the following.cn=nisd,ou=Rpc,dc=some,dc=domainThe oncRpcNumber and description attribute values are just simple assignmentsof the corresponding NIS+ column values. The rpc.nisd will collect the multipleNIS+ entries into one LDAP entry, with multiple cn values to represent the differentname column values.Similarly, the mapping from LDAP to NIS+ would be as follows.nisplusLDAPcolumnFromAttribute \rpc: cname=cn, \(name)=(cn), \number=oncRpcNumber, \comment=descriptionThe above assigns the oncRpcNumber and description values to thecorresponding NIS+ columns. The multi-valued cn (denoted by (cn) is mapped tomultiple name column values (denoted by (name)). Since the name column cannot bemulti-valued, the rpc.nisd creates one NIS+ entry for each cn value.Finally, the nisplusLDAPattributeFromColumn value is an example of rule setsused for deletion.nisplusLDAPattributeFromColumn \user_attr_del: dn=("uid=%s,", name), \SolarisUserQualifier=, \Chapter 16 • Transitioning From NIS+ to LDAP 263