13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CHAPTER 16Transitioning From <strong>NIS</strong>+ to <strong>LDAP</strong>This chapter describes how to make the transition from using the <strong>NIS</strong>+ naming serviceto <strong>LDAP</strong> naming services.<strong>NIS</strong>+ to <strong>LDAP</strong> OverviewThe <strong>NIS</strong>+ server daemon, rpc.nisd, stores <strong>NIS</strong>+ data in proprietary-format files inthe /var/nis/data directory. While it is entirely possible to keep <strong>NIS</strong>+ datasynchronized with <strong>LDAP</strong>, such synchronization has previously required an externalagent. However, the <strong>NIS</strong>+ daemon now enables you to use an <strong>LDAP</strong> server as a datarepository for <strong>NIS</strong>+ data. Since this makes it possible for <strong>NIS</strong>+ <strong>and</strong> <strong>LDAP</strong> clients toshare the same naming service information, it is easier to transition from using <strong>NIS</strong>+as the main naming service, to using <strong>LDAP</strong> for the same role.By default, the rpc.nisd daemon continues to work as before, relying only onthe/var/nis/data <strong>NIS</strong>+ database. If desired, the system administrator can choose touse an <strong>LDAP</strong> server as the authoritative data repository for any subset of the <strong>NIS</strong>+database. In this case, the /var/nis/data files serve as a cache for the rpc.nisddaemon, reducing <strong>LDAP</strong> lookup traffic, <strong>and</strong> enabling the rpc.nisd to continueworking if the <strong>LDAP</strong> server is temporarily unavailable. In addition to continuoussynchronization between <strong>NIS</strong>+ <strong>and</strong> <strong>LDAP</strong>, you can also perform uploads of <strong>NIS</strong>+ datato <strong>LDAP</strong>, or downloads of <strong>LDAP</strong> data to <strong>NIS</strong>+.Mapping of data to <strong>and</strong> from <strong>LDAP</strong> is controlled by a flexible configuration filesyntax. (All st<strong>and</strong>ard <strong>NIS</strong>+ tables (except for client_info.org_dir <strong>and</strong>timezone.org_dir) are covered by a template mapping file,/var/nis/<strong>NIS</strong>+<strong>LDAP</strong>mapping.template), which should require little or no changefor most <strong>NIS</strong>+ installations. (See “client_info <strong>and</strong> timezone Tables (<strong>NIS</strong>+ to<strong>LDAP</strong>)” on page 280 for information on client_info.org_dir <strong>and</strong>timezone.org_dir.) In addition to locations for <strong>NIS</strong>+ data in the <strong>LDAP</strong> <strong>Directory</strong>251

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!