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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TABLE 15–1 Terminology Related to the N2L TransitionTermDescription(Continued)st<strong>and</strong>ard mapsnonst<strong>and</strong>ard mapscustom map<strong>LDAP</strong> client<strong>LDAP</strong> namingservices clientN2L serverCommonly used <strong>NIS</strong> maps that are supported by the N2L service without requiringmanual modification to the mapping file. A list of supported st<strong>and</strong>ard maps is provided in“Supported St<strong>and</strong>ard Mappings” on page 232.St<strong>and</strong>ard <strong>NIS</strong> maps that are customized to use mappings between <strong>NIS</strong> <strong>and</strong> the <strong>LDAP</strong> DITother than the mappings identified in RFC 2307 or its successor.Any map that is not a st<strong>and</strong>ard map <strong>and</strong> therefore requires manual modifications to themapping file when transitioning from <strong>NIS</strong> to <strong>LDAP</strong>.Any traditional <strong>LDAP</strong> client that reads <strong>and</strong> writes to any <strong>LDAP</strong> server. A traditional <strong>LDAP</strong>client is a system that reads <strong>and</strong> writes to any <strong>LDAP</strong> server. A Solaris <strong>LDAP</strong> namingservices client h<strong>and</strong>les a customized subset of naming information.A Solaris <strong>LDAP</strong> client that h<strong>and</strong>les a customized subset of naming information.An <strong>NIS</strong> master server that has been reconfigured as an N2L server by using the N2Lservice. Reconfiguration includes replacing <strong>NIS</strong> daemons <strong>and</strong> adding new configurationfiles.<strong>NIS</strong>-to-<strong>LDAP</strong> Comm<strong>and</strong>s, Files, <strong>and</strong> MapsThere are two utilities, two configuration files, <strong>and</strong> a mapping that are associated withthe N2L transition.TABLE 15–2 Descriptions of N2L Comm<strong>and</strong>s, Files, <strong>and</strong> MapsComm<strong>and</strong>/File/Map/usr/lib/netsvc/yp/inityp2l/usr/lib/netsvc/yp/ypmap2src/var/yp/<strong>NIS</strong><strong>LDAP</strong>mapping/var/yp/ypservDescriptionA utility that assists with the creation of the <strong>NIS</strong><strong>LDAP</strong>mapping <strong>and</strong>ypserv configuration files. This utility is not a general-purpose tool forthe management of these files. An advanced user can maintain the N2Lconfiguration files or create custom mappings by using a text editor toexamine <strong>and</strong> customize the inityp2l output. See the inityp2l(1M)man page.A utility that converts st<strong>and</strong>ard <strong>NIS</strong> maps to approximations of theequivalent <strong>NIS</strong> source files. The primary use for ypmap2src is toconvert from an N2L transition server to traditional <strong>NIS</strong>. See theypmap2src(1M) man page.A configuration file that specifies the mapping between <strong>NIS</strong> mapentries <strong>and</strong> equivalent <strong>Directory</strong> Information Tree (DIT) entries in<strong>LDAP</strong>. See the <strong>NIS</strong><strong>LDAP</strong>mapping(4) man page.A file that specifies configuration information for the <strong>NIS</strong>–to–<strong>LDAP</strong>transition daemons. See the ypserv(4) man page.Chapter 15 • Transitioning From <strong>NIS</strong> to <strong>LDAP</strong> (Overview/Tasks) 231

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

Saved successfully!

Ooh no, something went wrong!