RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
After upgrading to the latest version of sudo, ldap and local users are not able to sudo

Version-Release number of selected component (if applicable):
sudo-1.8.19p2-10.el7.x86_64

How reproducible:
Everytime

Steps to Reproduce:
1. sudo su -

Actual results:
<username> is not in the sudoers file.  This incident will be reported.

Expected results:
Able to run sudo commands

Same issue with version:
* sudo-1.8.19p2-11.el7_4.x86_64

After downgrade all works:
 yum downgrade sudo-1.8.6p7-23.el7_3.x86_64

(In reply to grzegorz krol from comment #24)
> Same issue with version:
> * sudo-1.8.19p2-11.el7_4.x86_64

Are you using the ldap or sssd backend?

I'm using Dell Quest (vas4 module).

I see this issue with the LDAP backend. We do not use the SSSD backend because it doesn't respect the sudo option "!root_sudo". We also like to keep our standard bind user in sssd.conf different from the user that searches for SUDO rules in /etc/sudo-ldap.conf. We have also found that we are unable to restrict ACLs as tightly for the bind user in sssd.conf as we are in sudo-ldap.conf.