Learn more about these different git repos.
Other Git URLs
Commit 4f2951e made the SSSD treat all LDAP return codes except for LDAP_NO_SUCH_OBJECT as fatal. This was done to avoid deleting cached entries when the search for a valid object failed.
However, in case the LDAP server paging is misconfigured so that it only allows partial results to be returned, for example, the SSSD would completely abort the operation, too. The old version returned partial results, which might appear to the user as a regression.
We're going to special-case LDAP_SIZELIMIT_EXCEEDED and return partial results as 1.5.x did.
Fields changed
owner: somebody => jhrozek status: new => assigned
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=819063 (Red Hat Enterprise Linux 6)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=819063 819063]
patch: 0 => 1
Fixed in:
milestone: NEEDS_TRIAGE => SSSD 1.8.4 (LTM) resolution: => fixed status: assigned => closed
Metadata Update from @jhrozek: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.8.4 (LTM)
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/2364
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.
Login to comment on this ticket.