Bug 1123436

Summary: Applying the Configured sudo Policies to Hosts Using SSSD section do not include libsss_sudo installation
Product: Red Hat Enterprise Linux 6 Reporter: Javier Ramirez <javier.ramirez>
Component: doc-Identity_Management_GuideAssignee: Tomas Capek <tcapek>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6CC: jhrozek
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-31 16:56:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Javier Ramirez 2014-07-25 15:55:08 UTC
Description of problem:
the RHEL6 Identity Management Guide, chapter 20.4.2 , "Applying the Configured sudo Policies to Hosts Using SSSD" provides instructions on how to configure sudo to use SSSD.  However, these instructions do not work unless libsss_sudo is installed. 

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.5
Identity Management Guide
Managing Identity and Authorization Policies for Linux-Based Infrastructures
Edition 3.0.0

How reproducible:
Always

Steps to Reproduce:
1. Follow documentation at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/config-sudo-clients.html#example-configuring-sudo-sssd
2. Try to sudo
3. Observe error "sudo: Unable to dlopen /usr/lib64/libsss_sudo.so"
4. After installing libsss_sudo

Actual results:
"sudo: Unable to dlopen /usr/lib64/libsss_sudo.so"

Expected results:
Error should not occur, and if sudo is properly configured, access should be granted.

Additional info:
"yum install libsss_sudo" corrects error.

Comment 1 Javier Ramirez 2014-07-25 16:09:59 UTC
Please forget about step #4 of Steps to reproduce, it comes from a copy&paste error