#2100 sudo responder does not support specifying just one of sudoNotBefore/sudoNotAfter
Closed: Fixed Opened by jhrozek.

Nikolai found out that sudo-ldap allows specifying just one of the two attributes. SSSD requires both.


Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=877438 (Red Hat Enterprise Linux 7)

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=877438 877438]

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.2

Fields changed

owner: somebody => pbrezina
status: new => assigned

Fields changed

patch: 0 => 1

  • master: d1f3610aefcb634f212d4c099fac102b3e4dee59
  • sssd-1-11: 9f3e9e9984e48bb45c6c3fb8f49b0ff5bf337393

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => When a sudo rule is restricted by time using the sudoNotBefore/sudoNotAfter attribute, just one of these is required, which is what the traditional ldap backend requires as well.

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.11.2

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

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.

Metadata