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 860386 - new /etc/sudo-ldap.conf configuration file problems
Summary: new /etc/sudo-ldap.conf configuration file problems
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Identity_Management_Guide
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-25 17:51 UTC by Fred van Zwieten
Modified: 2013-03-01 00:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-01 00:33:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fred van Zwieten 2012-09-25 17:51:12 UTC
Description of problem:
Bug 760843 (https://bugzilla.redhat.com/show_bug.cgi?id=760843) is CLOSED ERRATA. It is released in ERRATA http://rhn.redhat.com/errata/RHBA-2012-0905.html. However, the changes have multiple problems:

1. De most severe is that the Identity Management Guide is not updated to this new situation. Especially the instructions to configure ipa clients for sudo thru ldap (https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Identity_Management_Guide/index.html#Setting_up_sudo_Rules-Client_Configuration_for_sudo_Rules). 

2. The newly installed /etc/sudo-ldap.conf has some of the entries from the old /etc/nslcd.conf, but not all. However, all the entries from the documentation are needed. It would be nice is that is reflected in the file commented out entries.

3. The permissions of /etc/sudo-ldap does not seem to be correct. It is 440. Shouldn't it be 640?


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


How reproducible:


Steps to Reproduce:
1. Read par 13.4.2 of Identity Management Guide for RHEL6.3
2. Configure system accordingly
3. See if it works (it doesn't)
  
Actual results:
Sudo does not query IPA for sudo data

Expected results:
Sudo queries IPA for sudo data and acts accordingly

Additional info:
I have today spent a good 4 hours trying to get this to work just to find out why it didn't. Not funny!! I do not understand this process. Why are errata released without adjusting the documentation accordingly?

Comment 2 Rob Crittenden 2012-09-25 18:12:29 UTC
Re-assigning component to documentation.

The second two problems need to be handled in the sudo package. I filed https://bugzilla.redhat.com/show_bug.cgi?id=860397 and cc'd you on it.

Comment 4 Deon Ballard 2013-03-01 00:33:55 UTC
Mass closure.


Note You need to log in before you can comment on or make changes to this bug.