On 09/21/2013 04:38 PM, Rowland Penny wrote:
> On 20/09/13 08:36, Pavel Březina wrote:
>> On 09/19/2013 06:18 PM, Rowland Penny wrote:
>>> Ok, I am back again, trying to get sssd to control sudo, but failing.
>>> I added the sudo active directory schema ldif to samba4 AD
>>> then added this:
>>> dn: OU=SUDOers,DC=example,DC=com
>>> objectClass: top
>>> objectClass: organizationalUnit
>>> ou: SUDOers
>>> dn: CN=linuxusers,OU=SUDOers,DC=example,DC=com
>>> objectClass: top
>>> objectClass: sudoRole
>>> cn: linuxusers
>>> sudoUser: %linuxusers
>>> sudoHost: ALL
>>> sudoCommand: ALL
>>> On a Linux Mint client:
>>> sudo apt-get install sudo-ldap
>>> Edited /etc/sudo-ldap.conf
>>> # TLS certificates (needed for GnuTLS)
>>> TLS_CACERT /etc/ssl/certs/ca-certificates.crt
>>> BASE DC=example,DC=com
>>> URI ldap://server.example.com
>>> LDAP_VERSION 3
>>> SUDOERS_BASE ou=SUDOers,DC=example,DC=com
>>> SUDOERS_SEARCH_FILTER (&(objectClass=sudoRole))
>>> BINDDN CN=Administrator,CN=Users,DC=example,DC=com
>>> BINDPW xxxxxxxxxx
>>> then edited /etc/nsswitch.conf and added
>>> sudoers: files ldap
>>> restarted sudo
>>> then as a normal user, tried to run a command with sudo, this worked.
>>> I then altered /etc/sssd/sssd.conf and added
>>> services = nss, pam, autofs, sudo
>>> ldap_sudo_search_base = OU=SUDOers,DC=example,DC=com
>>> altered /etc/nsswitch.conf
>>> sudoers: files sss
>>> restarted sssd
>>> restarted sudo
>>> tried to run the command with sudo again, this time it failed
>>> having been bitten by the way autofs works, I went straight to the way
>>> that sudo & sssd do the ldapsearch:
>>> sudo searches with objectClass=sudoRole & sudoUser attribute
>>> sssd searches with objectClass=sudoRole & sudoHost attribute
>>> Now I understand that the sssd search for the sudoHost attribute is to
>>> ensure that only sudo rules for the host are downloaded, but it
>>> actually seem to download any rules.
>>> Is there anyway I can get the sssd search to include the sudoUser
>>> attribute in the same way that the sudo ldap search does?
>> no, it is not desirable. SSSD periodically downloads all rules that
>> are applicable to the machine, and then filters them by user when sudo
>> request is performed. In other words: filtering by sudoUser is there,
>> only on other place (sssd_sudo process).
>> Can you send us (sanitized or privately if you want) your complete
>> sssd.conf, sssd_yourdomain.log and sssd_sudo.log please?
>>> Or can anybody tell me where I am going wrong (again).
>> sssd-users mailing list
> OK, I have now got sssd to cache the sudo rules from AD, I found out
> that you must have 'defaults' in the AD database, I didn't and thought
> you could just use the defaults on the client.
having cn=defaults in LDAP is not necessary. From the logs you've sent
me, I can see that three rules were stored in the cache.
If the rules are not stored when cn=defaults is missing, it is a bug.
However, I am unable to reproduce it.
> Now, even though sssd has cached the rules, I still cannot get an AD
> user to run a command as the root user.
> Anybody got any further ideas? or to put it another way, HELPPPPP!!!!!!
Please, see my earlier response.
sssd-users mailing list
Hi, I am fairly sure that I have fixed my problem, it is not a sssd
problem, it is an ubuntu problem.
I was using 'sudo-ldap' as you need this to connect via ldap, so I
assumed I needed it to connect via sssd, this it would seem is wrong.
I found this:
Superseded in raring-release on 2012-12-08
Deleted in raring-proposed on 2012-12-09 (Reason: moved to release)
sudo (1.8.6p3-0ubuntu1) raring; urgency=low
* New upstream release (1.8.6p3).
* Add patch to fix building with sssd when ldap is disabled.
* Drop sudo.manpages and sudo-ldap.manpages as the upstream build system
now does the right thing here.
* Build the main sudo package with support for sssd, this doesn't add any
additional build time or runtime dependency. sudo will dynamically load
the sssd library if 'sss' is listed for the 'sudoers' nss service.
-- Stephane Graber <email address hidden> Fri, 16 Nov 2012 09:31:32
Hmm, the 'sudo' package seems to be built to connect to sssd.
Re-installed the 'sudo' package and it now seems to work, so I can only
surmise that the 'sudo-ldap' package isn't built to connect to sssd for
It would make more sense to build (well to me anyway) a 'sudo-sssd'
package OR just one 'sudo' package.