Bug 1020366

Summary: redhat6 sudo over sssd doesn't work : libsss_sudo missing
Product: Red Hat Enterprise Linux 6 Reporter: guillard <orglube>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED NOTABUG QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.6CC: grajaiya, jgalipea, lslebodn, mkosek, pbrezina
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-17 15:13:31 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 guillard 2013-10-17 14:17:54 UTC 
Description of problem:

when configuring to instruct sudo to gather sudo rules
over sssd, I get the folowing error message :

# sudo ls /etc/sssd

sudo: Unable to dlopen /usr/lib64/libsss_sudo.so: (null)
sudo: Unable to initialize SSS source. Is SSSD installed on your machine?


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

sssd-1.9.2-82.7.el6_4.x86_64

How reproducible:

Steps to Reproduce:
1. yum install sssd sudo sssd-client pam nss
2. echo "sudoers:   sss files" >> /etc/nsswitch.conf
3. add appropriate "sudo_provider" and "ldap_sudo_search_base" to sssd.conf
4. add "sudo" to "services =" in sssd.conf
5. echo "[sudo]" >> /etc/sssd/sssd.conf

Actual results:

sudo: Unable to dlopen /usr/lib64/libsss_sudo.so: (null)

Expected results:

grant access based on sudo rules found in sssd

Additional info:

To fix this bug, download and install libsss_sudo (from
rpmfind for example : tested with libsss_sudo-1.9.2-82.10).


Normally, libsss_sudo should be packaged within redhat
sudo package.
Comment 2 Jakub Hrozek 2013-10-17 15:13:31 UTC 
In RHEL6, you need to install libsss_sudo yourself, in later releases we moved the library back to the SSSD itself.

Not a bug, sorry for the inconvenience.