You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sudo uses the LDAP back end it reads an option called SUDOERS_TIMED from ldap.conf. If this option is on, the search filters also include attributes such as sudoNotBefore and sudoNotAfter.
We should add a similar option to the SUDO responder. The responder already includes code to construct the modified search filter (get_sudo_time_filter)
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1116
When sudo uses the LDAP back end it reads an option called SUDOERS_TIMED from ldap.conf. If this option is on, the search filters also include attributes such as sudoNotBefore and sudoNotAfter.
We should add a similar option to the SUDO responder. The responder already includes code to construct the modified search filter (
get_sudo_time_filter
)Comments
Comment from dpal at 2012-01-05 15:48:55
Fields changed
blockedby: =>
blocking: =>
milestone: NEEDS_TRIAGE => SSSD 1.8 SUDO Support
Comment from pbrezina at 2012-01-13 11:12:36
Fields changed
owner: somebody => pbrezina
status: new => assigned
Comment from pbrezina at 2012-01-17 18:00:23
Fields changed
patch: 0 => 1
Comment from dpal at 2012-01-19 03:12:53
Fields changed
rhbz: => 0
Comment from jhrozek at 2012-01-31 15:57:31
Fields changed
owner: pbrezina => jhrozek
status: assigned => new
Comment from jhrozek at 2012-01-31 15:57:39
Fields changed
status: new => assigned
Comment from pbrezina at 2012-02-06 10:57:07
Fixed by
_comment0: Fixed in c9aab1c => 1328522315850077
feature_milestone: =>
resolution: => fixed
status: assigned => closed
Comment from jhrozek at 2017-02-24 14:32:29
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: