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.

nisplus<strong>LDAP</strong>objectDN rpc:ou=Rpc,?one?objectClass=oncRpc:\ou=Rpc,?one?objectClass=onRpc,objectClass=topThe above shows that the table entries are read from <strong>and</strong> written to the base ou=Rpc.Again, the trailing comma appends the defaultSearchBase value. Select entriesthat have an objectClass attribute value of oncRpc. When creating an entry in theou=Rpc container in <strong>LDAP</strong>, you also must specify top as an objectClass value.As an example showing a non-default delete specification, consider the following.nisplus<strong>LDAP</strong>objectDNuser_attr:\ou=People,?one?objectClass=SolarisUserAttr,\solarisAttrKeyValue=*:\ou=People,?one?objectClass=SolarisUserAttr:\dbid=user_attr_delThe user_attr.org_dir data resides in the ou=People <strong>LDAP</strong> container, which itshares with account information from other sources, such as the passwd.org_dir<strong>NIS</strong>+ table.Select entries in that container that have the solarisAttrKeyValue attribute, sinceonly those contain user_attr.org_dir data. The dbid=user_attr_del portionof the nisplus<strong>LDAP</strong>objectDN shows that when an entry in theuser_attr.org_dir <strong>NIS</strong>+ table entry is deleted, deletion of the corresponding<strong>LDAP</strong> entry (if any) should follow the rules in the rule set identified by theuser_attr_del database ID. See “nisplus<strong>LDAP</strong>columnFromAttributeAttribute” on page 262 for more information.nisplus<strong>LDAP</strong>attributeFromColumn Attributenisplus<strong>LDAP</strong>attributeFromColumn specifies the rules used to map <strong>NIS</strong>+ data to<strong>LDAP</strong>. Mapping rules for the other direction is controlled bynisplus<strong>LDAP</strong>columnFromAttribute.nisplus<strong>LDAP</strong>columnFromAttribute Attributenisplus<strong>LDAP</strong>columnFromAttribute specifies the rules used to map <strong>LDAP</strong> data to<strong>NIS</strong>+.The full entry mapping syntax can be found on <strong>NIS</strong>+<strong>LDAP</strong>mapping(4). However, afew examples should make things clearer.The <strong>NIS</strong>+ rpc.org_dir table contains four columns called cname, name, numbe, <strong>and</strong>comment. Therefore, the entries for the <strong>NIS</strong>+ RPC program number (100300) with thecanonical name nisd <strong>and</strong> the aliases rpc.nisd <strong>and</strong> nisplusd could be representedby the following <strong>NIS</strong>+ entries in rpc.org_dir.nisd nisd 100300 <strong>NIS</strong>+ servernisd rpc.nisd 100300 <strong>NIS</strong>+ servernisd nisplusd 100300 <strong>NIS</strong>+ server262 System Administration Guide: <strong>Naming</strong> <strong>and</strong> <strong>Directory</strong> <strong>Services</strong> (<strong>DNS</strong>, <strong>NIS</strong>, <strong>and</strong> <strong>LDAP</strong>) • January 2005

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

Saved successfully!

Ooh no, something went wrong!