Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product RHEL RFE): Bug 1132264
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: - In RHEL 6.5 configured as ldap-client using sssd, there are some local users whose sudo rules are stored/defined on LDAP server. sssd is not fetching those sudo rules from ldap server if the users are local to system. - At this stage, SSSD only supports sudo rules and users being in the same domain. Add this feature of retrieving sudo rules for local users in sssd. - The local users do not have account ( duplicate account ) on ldap server. Version-Release number of selected component (if applicable): sssd-1.9.2-129.el6_5.4.x86_64 How reproducible: Steps to Reproduce: 1. configure rhel6 as ldap client, and also configure it to fetch sudo rules from ldap server 2. create local users on rhel6 and add define their sudo rules on ldap server. 3. Try to fetch these sudo rules from rhel6 client. Actual results: local user is not able to run the sudo rules: ]# sudo -l -U testuser User testuser is not allowed to run sudo on localsystem Expected results: Local user should be able to run the sudo rules. Additional info: - At this stage, this feature is available with nss-pam-ldap. As per discussion with Jakub, this feature will be included in version 1.13.
Depends on the feature to manage local users.
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 milestone: NEEDS_TRIAGE => SSSD 1.13 beta review: True => 0 selected: => testsupdated: => 0
Fields changed
blockedby: => #2228
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the 1.13 release to 1.14
milestone: SSSD 1.13 backlog => SSSD 1.14 beta
priority: major => minor sensitive: => 0
This will happen for free when we support local users.
milestone: SSSD 1.14 beta => SSSD 1.15 beta
Metadata Update from @dpal: - Issue marked as depending on: #2228 - Issue set to the milestone: SSSD Future releases (no date set yet)
Putting into 1.16 (next major upstream). I suspect this is actually done since the files provider was implemented, but we need to re-test.
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue set to the milestone: SSSD 1.16.0 (was: SSSD Future releases (no date set yet))
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: postpone-to-2-0
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue untagged with: postpone-to-2-0 - Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
This has been working for a long time..
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: worksforme - 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/3536
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.
Log in to comment on this ticket.