Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=880335 (Red Hat Enterprise Linux 6)
Description of problem: %#group_id values of sudoUser attribute are not supported - sudo rules with these values never match Version-Release number of selected component (if applicable): libsss_autofs-1.9.2-21.el6.x86_64 libsss_idmap-1.9.2-21.el6.x86_64 sssd-1.9.2-21.el6.x86_64 sssd-client-1.9.2-21.el6.x86_64 libsss_sudo-1.9.2-21.el6.x86_64 sudo-1.8.6p3-5.el6.x86_64 How reproducible: always 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 "su -c 'sudo -u user2 true' user1 && echo allowed || echo denied" as root. Actual results: denied Expected results: allowed Additional info: The attached LDIF file has memberUid attribute explicitly referring to the primary group's (group_user1) user (user1) to workaround Bug 880176. The bare LDAP sudo backend works with this. Trac ticket: https://fedorahosted.org/sssd/ticket/1667
Fields changed
blockedby: => blocking: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.12 beta priority: major => minor testsupdated: => 0
milestone: SSSD 1.12 beta => SSSD 1.13 beta
Reassigning to Michal who is working on #1108. This is a low-priority task that could be done along with #1108.
changelog: => owner: somebody => mmsrubar review: => 0 selected: =>
I don't thin we will implement this unless a patch is provided, I suggest to defer.
mark: => 0 review: 0 => 1 selected: => May sensitive: => 0
milestone: SSSD Future releases (no date set yet) => SSSD Patches welcome
Metadata Update from @jhrozek: - Issue assigned to mmsrubar - Issue set to the milestone: SSSD Patches welcome
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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: - https://github.com/SSSD/sssd/issues/2720
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.