#4046 sudo: incorrect usn value for openldap
Closed: Fixed a year ago by pbrezina. Opened a year ago by pbrezina.

Steps to reproduce:

  1. install openldap server
  2. run sssd
  3. there are no sudo rules on the server and there are no cached objects
  4. you'll see in the logs that sudo smart refresh uses (&(&(objectclass=sudoRole)(modifyTimestamp>=1))... filter (1 instead of proper datetime value)

When a new rule is added OpenLDAP server will fail to evaluate the filter because it can not compare modifyTimestamp to non-datetime value.

389-ds works fine.


Metadata Update from @pbrezina:
- Issue assigned to pbrezina

a year ago

Metadata Update from @pbrezina:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Metadata Update from @lslebodn:
- Issue status updated to: Open (was: Closed)

a year ago

Darn, I pushed it to github. Thank Lukas, it is fixed.

Metadata Update from @pbrezina:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year 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/5014

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