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

■■Chapter 4, for an overview of NISChapter 8, for an overview of LDAPWhen Not to Use the NIS-to-LDAP ServiceDo not use the N2L service in these situations:■■■In an environment where there is no plan to share data between NIS and LDAPnaming services clientsIn such an environment, an N2L server would serve as an excessively complex NISmaster server.In an environment where NIS maps are managed by tools that modify the NISsource files (other than yppasswd)Regeneration of NIS sources from DIT maps is an imprecise task that requiresmanual checking of the resulting maps. Once the N2L service is used, regenerationof NIS sources is provided only for backout or reverting to NIS.In an environment with no NIS clientsIn such an environment, use Solaris LDAP naming services clients and theircorresponding tools.Effects of the NIS-to-LDAP Service on UsersSimply installing the files that are related to the N2L service does not change the NISserver’s default behavior. At installation, the administrator will see some changes toNIS man pages and the addition of N2L helper scripts, inityp2l and ypmap2src,on the servers. But as long as inityp2l is not run or the N2L configuration files arenot created manually on the NIS server, the NIS components continue to start intraditional NIS mode and function as usual.After inityp2l is run, users see some changes in server and client behavior.Following is a list of NIS and LDAP user types and a description of what each type ofuser should notice after the N2L service is deployed.User TypeNIS master server administratorsEffect of N2L ServiceThe NIS master server is converted to an N2L server. TheNISLDAPmapping and ypserv configuration files are installed onthe N2L server. After the N2L server is established, you can useLDAP commands to administer your naming information.Chapter 15 • Transitioning From NIS to LDAP (Overview/Tasks) 229