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

NAME ’nisplusClientInfoData’ \DESC ’NIS+ client_info table data’ \SUP top STRUCTURAL MUST ( cn ) \MAY ( nisplusClientInfoAttr $ nisplusClientInfoInfo $ nisplusClientInfoFlags ) )To create the container, put the following LDIF data in a file. Substitute your actualsearch base for searchBase.dn: ou=ClientInfo, searchBaseobjectClass: organizationalUnitou: ClientInfoobjectClass: topUse the above file as input to the ldapadd command in order to create theou=ClientInfo container. For example, if your LDAP administrator DN iscn=directory manager, and the file with the LDIF data is called cifile, dothefollowing.# ldapadd -D cn="directory manager" -f cifileDepending on the authentication required, the ldapadd command might prompt fora password.The /var/nis/NIS+LDAPmapping.template file contains commented-outdefinitions for the client_info.org_dir table. Copy these to the actual mappingfile, enable by removing the comment character ’#’, and restart the rpc.nisddaemon.# svcadm restart network/rpc/nisplus:defaultIf necessary, synchronize NIS+ and LDAP data as described in “NIS+ to LDAPMigration Scenarios” on page 264.timezone Attributes and Object ClassCreate attributes and object class as below, and then create the container for thetimezone data. The suggested container name is ou=Timezone. (The LDIF data issuitable for ldapadd(1). Attribute and object class OIDs are examples only.)dn: cn=schemachangetype: modifyadd: attributetypesattributetypes: ( 1.3.6.1.4.1.42.2.27.5.42.42.15.0 NAME ’nisplusTimeZone’ \DESC ’tzone column from NIS+ timezone table’ \SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )dn: cn=schemachangetype: modifyChapter 16 • Transitioning From NIS+ to LDAP 281