#1646 [RFE] Leverage GPO policies to define SUDO rules
Closed: wontfix 4 years ago by pbrezina. Opened 11 years ago by dpal.

Once ticket #1644 is addressed and generic GPO download mechanism is available the GPO can be used to manage deliver and enforce SUDO policies. Some vendors allow GPO to contain a whole sudoers file that gets downloaded and applied to the client system. Such approach however seems suboptimal. It would make sense to use the same model as the one used in IPA and have the sudo rules presented in a more structured way so that they can be filtered and uploaded into the SSSD cache and served from that storage to SUDO utility via SSSD <-> SUDO integration feature.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta
owner: somebody => yelley

Fields changed

rhbz: => todo

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 0

Fields changed

changelog: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => minor
review: => 0

Mass-moving tickets not planned for the next two releases.

Please reply with a comment if you disagree about the move..

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

I don't think we would implement this unless patches are provided.

review: 0 => 1
selected: Not need => May
sensitive: => 0

Fields changed

milestone: SSSD Future releases (no date set yet) => SSSD Patches welcome

Metadata Update from @dpal:
- Issue assigned to yelley
- Issue set to the milestone: SSSD Patches welcome

7 years ago

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)

4 years ago

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/2688

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.

Login to comment on this ticket.

Metadata