RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 665465 - nss_ldap provides nis capabilities, but neglects to set the nisdomainname
Summary: nss_ldap provides nis capabilities, but neglects to set the nisdomainname
Keywords:
Status: CLOSED DUPLICATE of bug 704919
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nss-pam-ldapd
Version: 6.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-23 22:51 UTC by Jr Aquino
Modified: 2012-06-29 14:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-29 14:38:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jr Aquino 2010-12-23 22:51:17 UTC 
Description of problem:
nss_ldap allows for nis content to be stored correctly in LDAP, however, a subtle yet important piece is missing.  nisdefaultdomain is left unset.  The only way to achieve this is to:
A. manually set defaultdomain domain.com at the cli <- doesn't survive reboot.
B. configure the client as if it was a nis / yp client complete with yp.conf file expecting a <nis> server to be available.

/etc/sysconfig/network allows for the variable NISDOMAIN to be set, but the only init code that appears to call it is the ypbind piece.

Version-Release number of selected component (if applicable):


How reproducible / Steps to Reproduce:
/etc/ldap.conf:
nss_base_netgroup $DN-DATA

/etc/nsswitch.conf:
netgroup:   ldap

/etc/sysconfig/network:
NISDOMAIN=domain.com

getent netgroup <netgroup-name>

domainname or nisdomainname cli returns (none)
  
Actual results:
getent netgroup <netgroup-name>
 - returns proper nisnetgrouptriple

domainname or nisdomainname cli:
 -returns (none)

Expected results:
getent netgroup <netgroup-name>
 - returns proper nisnetgrouptriple

domainname or nisdomainname cli:
 -returns nisnetgroupname


Additional info:
If /etc/sysconfig/network contains the NISDOMAIN var, then the internal system should set that without having to be called specifically from the ypbind init script.
Comment 3 Bill Nottingham 2012-06-29 14:38:39 UTC 

*** This bug has been marked as a duplicate of bug 704919 ***
Note You need to log in before you can comment on or make changes to this bug.