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.

<strong>NIS</strong>+ Entry Owner, Group, Access, <strong>and</strong>TTLWhen <strong>NIS</strong>+ table entries are created from <strong>LDAP</strong> data, the default behavior is toinitialize the entry object owner, group, access rights, <strong>and</strong> TTL using thecorresponding values from the table object in which the entry object lives. This isnormally sufficient, but there might be cases where these <strong>NIS</strong>+ entry attributes mustbe established individually. An example of this would be a site that did not use therpc.nispasswdd(1M) daemon. In order to allow individual users to change their<strong>NIS</strong>+ passwords (<strong>and</strong> re-encrypt their Diffie-Hellman keys stored in thecred.org_dir table), passwd.org_dir <strong>and</strong> cred.org_dir entries for the usershould be owned by the user, <strong>and</strong> have modify rights for the entry owner.If you need to store table entry owner, group, access, or TTL in <strong>LDAP</strong> for one or more<strong>NIS</strong>+ tables, you need to do the following.▼How to Store Additional Entry Attributes in <strong>LDAP</strong>1. Consult your <strong>LDAP</strong> server documentation, <strong>and</strong> create the following newattributes <strong>and</strong> object class. (LDIF data is suitable for ldapadd. Attribute <strong>and</strong>object class OIDs are for illustration only.)dn: cn=schemachangetype: modifyadd: attributetypesattributetypes: ( 1.3.6.1.4.1.42.2.27.5.42.42.4.0 NAME ’nisplusEntryOwner’ \DESC ’Opaque representation of <strong>NIS</strong>+ entry owner’ \SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )attributetypes: ( 1.3.6.1.4.1.42.2.27.5.42.42.4.1 NAME ’nisplusEntryGroup’ \DESC ’Opaque representation of <strong>NIS</strong>+ entry group’ \SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )attributetypes: ( 1.3.6.1.4.1.42.2.27.5.42.42.4.2 NAME ’nisplusEntryAccess’ \DESC ’Opaque representation of <strong>NIS</strong>+ entry access’ \SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )attributetypes: ( 1.3.6.1.4.1.42.2.27.5.42.42.4.3 NAME ’nisplusEntryTtl’ \DESC ’Opaque representation of <strong>NIS</strong>+ entry TTL’ \SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )dn: cn=schemachangetype: modifyadd: objectclassesobjectclasses:(1.3.6.1.4.1.42.2.27.5.42.42.5.0 NAME ’nisplusEntryData’\SUP top STRUCTURAL DESC ’<strong>NIS</strong>+ entry object non-column data’\MUST ( cn ) MAY ( nisplusEntryOwner $ nisplusEntryGroup $\nisplusEntryAccess $ nisplusEntryTtl ) )Chapter 16 • Transitioning From <strong>NIS</strong>+ to <strong>LDAP</strong> 275

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

Saved successfully!

Ooh no, something went wrong!