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 736672 - nslcd fails to start if it has keywords as 'sudoers_base' and 'sudoers_debug'.
Summary: nslcd fails to start if it has keywords as 'sudoers_base' and 'sudoers_debug'.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nss-pam-ldapd
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-08 11:55 UTC by Gowrishankar Rajaiyan
Modified: 2011-09-08 16:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-08 16:38:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Gowrishankar Rajaiyan 2011-09-08 11:55:57 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
# rpm -q sudo nss-pam-ldapd
sudo-1.7.4p5-7.el6.i686
nss-pam-ldapd-0.7.5-9.el6.i686

How reproducible:
Always

Steps to Reproduce:
1. Configure /etc/nslcd.conf as:
# grep ^[^#] /etc/nslcd.conf 
uid nslcd
gid ldap
sudoers_base ou=SUDOers,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com
binddn uid=sudo,cn=sysaccounts,cn=etc,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com
bindpw bind123
ssl no
tls_cacertfile /etc/ipa/ca.crt
bind_timelimit 5
timelimit 15
BASE dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com
TLS_CACERTDIR /etc/ipa
uri ldap://bumblebee.lab.eng.pnq.redhat.com

2. service nslcd restart
3.
  
Actual results:
# service nslcd restart
Stopping nslcd:                                            [  OK  ]
Starting nslcd: nslcd: /etc/nslcd.conf:132: unknown keyword: 'sudoers_base'
                                                           [FAILED]

However, sudo works as expected if you have "sudoers_base" and "sudoers_debug" in /etc/nslcd.conf. 


Expected results:
nslcd should recognize these keywords.

As per the fix in https://bugzilla.redhat.com/show_bug.cgi?id=709235 sudo now searches the /etc/nslcd.conf file, hence the sudoers_base and sudoers_debug keywords should be recognized and nslcd should start without any failures.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=709235
Comment 2 Nalin Dahyabhai 2011-09-08 16:38:35 UTC 
sudo needs to have its own configuration file.  Depending on configuration files from other packages which may or may not be installed (and requiring nslcd so that its configuration file will be there, even if the system uses something else like SSSD) will inevitably break.
Note You need to log in before you can comment on or make changes to this bug.