Just an update, the sudo rules using groups worked in SSSD but not pam ldap. On May 22, 2013, at 10:15 PM, Dan Lavu < dan@xxxxxxxx> wrote: John,
Thanks for all the info. I'm running a very similar setup but I'm still using the legacy sudo-ldap.conf for my sudo info, I'll install sudo-sss and give that a whirl.
Dan
we're using sssd for Kerberos logins with LDAP user account details, and it's caching sudo LDAP for us too. I'm not sure off hand if it'll work with nested groups if you use them - we haven't used nested groups on any of the groups we've used with sudo (due to other various programs failing to support either recursing through groups or using the memberof attribute on the user).
For that example I gave before, the other sudo values are: sudocommand: ALL sudohost: ALL
On other sudoroles we have specific commands and hosts too. We're not using any other sudo attributes on our sudoroles at the moment (we actually need to update the schema for the version of sudo we're running, since it expectes sudorunasuser and sudorunasgroup rather than sudorunas, for example).
On Wed, May 22, 2013 at 7:54 PM, Dan Lavu <dan@xxxxxxxx> wrote:
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
|
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
