Sudo fails with message "user is not in the sudoers file. This incident will be reported."
Can be seen where there is a native version of sudo installed on the same machine. '/opt/quest/bin/sudo' does not read from the native '/etc/sudoers' but rather from it's own sudoers file '/etc/opt/quest/sudo/sudoers'
The common occurance is that admins believe that quest sudo is reading from '/etc/sudoers' and can't understand why it is not working for the groups and users they are testing. What is happening is that quest sudoers file is empty or just has commented out default information.
The easiest resolution is to symbolically link the two files.
ln -s /etc/sudoers /etc/opt/quest/sudo/sudoers
You can also update them manually or copy over this info but the preferred method is to link them so all the changes are in both.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center