Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=880176 (Red Hat Enterprise Linux 6)
Description of problem:
sudo rules with %group_name or %#group_id sudoUser don't match for primary
groups not having user's memberUid.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use attached LDIF file to fill LDAP directory.
2. Use attached sssd.conf as the base for client configuration.
3. Execute Execute "su -c 'sudo -u user2 true' user1 && echo allowed || echo
denied" as root.
If the primary group (group_user1) has a memberUid with user name (user1)
added, the above works as expected.
This will still not work with sudoUser specified as group ID (i.e. %#20001),
even with memberUid added, because of
design_review: => 0
milestone: NEEDS_TRIAGE => SSSD 1.9.4
testsupdated: => 0
owner: somebody => pbrezina
patch: 0 => 1
status: new => assigned
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.9.4
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.