[SSSD-users] SSD / chown on initial automated installation

Hi sssd-users, i'm using SSSD for the auth on our compute clusters - about 130 nodes in total. The installation is done by Foreman and Puppet. Most of our clusters are on CentOS 7.3 and we are planning to upgrade to 7.4 by reinstall all nodes. Here is my question: In my puppet scripts i'm

[SSSD-users] Re: sudo for Active Directory group

We found that there was a Sudo change that requires fqdn for hostnames. Older versions used short names. Does having both fqdn and short names make it work? Sent from my iPhone > On Dec 22, 2017, at 6:12 AM, Jakub Hrozek wrote: > > EXTERNAL MAIL:

[SSSD-users] Re: sudo for Active Directory group

Ah, since you’re using local sudo rules and not stored in AD, I think only the sudo log would be most interesting. Plus, is the user either a member of wheel or linux_admin? (iow, do either of these group show up if you run ‘id’ as the user?) > On 22 Dec 2017, at 15:09, Jakub Hrozek

[SSSD-users] Re: sudo for Active Directory group

If you follow https://docs.pagure.org/SSSD.sssd/users/sudo_troubleshooting.html and generate the sssd logs, does that shed some more light? > On 22 Dec 2017, at 14:48, Viktor Ekl wrote: > > Hello. > > Sssd 1.15.2-50 on Centos 7. I'm trying to grant sudo access to

[SSSD-users] sudo for Active Directory group

Hello. Sssd 1.15.2-50 on Centos 7. I'm trying to grant sudo access to members of known AD group (say, "linux_admin"), but with no success: " is not allowed to run sudo on . This incident will be reported" Can't understand why, according to sssd_domain.log group and members found ? My