Posted on 02-26-2020 07:55 AM
Since updating to 10.15.3 we have been unable to sudo using an AD admin group. After the update we noticed that the admin accounts were not able to elevate. Running dsconfigad -groups "DOMAINdomain admins" has fixed the elevation issue but we are still getting "account is not in the sudoers file..." when we try to sudo.
I have followed various guides trying to fix this and basically where I have ended up is, if I put a username in the sudoers file it works but if I put an AD group in it doesn't.
I am using a command sent from jamf to create a file in sudoers.d and then echo the group in like this: touch /etc/sudoers.d/file | echo "account ALL = (ALL) ALL" > /etc/sudoers.d/file
If I replace "account" with a domain group: touch /etc/sudoers.d/file | echo "%DOMAINADGroup ALL = (ALL) ALL" > /etc/sudoers.d/file I get the same message about it not being in the sudoers file. I have followed every guid I can find for adding a domain group to the sudoers file but none seem to work. Any suggestions are appreciated!
Posted on 02-27-2020 04:54 AM
I find that if you are setting AD Groups to be admin it can be really hit or miss with macOS unless you make sure to add the AD Group directly to the local Admin group. Then it works perfectly.
sudo dseditgroup -o edit -a "DOMAINdomain admins" -t group admin
Give that a try, only needs to be ran once per computer. But the computers must be connected to the domain for Admin privileges to work.