#1201 When ldap_parse_result fails, user search returns ENOENT and deletes valid entry
Closed: Fixed None Opened 12 years ago by jhrozek.

I've seen this happening on my laptop. Apparently the user entry was removed after a search returned ENOENT and a new one without the cachedPassword attribute was saved afterwards. I referenced the createTimestamp attribute of the sysdb entry with logs and I saw this:

(Sat Feb 18 23:32:02 2012) [sssd[be[redhat.com]]] [sdap_get_generic_ext_done]
(0x0400): Search result: Server is unwilling to perform(53), Simple
Paged Results Search already in progress on this connection
(Sat Feb 18 23:32:02 2012) [sssd[be[redhat.com]]] [sdap_get_generic_ext_done]
(0x0040): Unexpected result from ldap: Server is unwilling to perform(53),
Simple Paged Results Search already in progress on this connection
(Sat Feb 18 23:32:02 2012) [sssd[be[redhat.com]]] [sdap_get_users_process]
(0x0400): Search for users, returned 0 results.

From the log it seems clear that the request was marked as done after it found
no users, otherwise there would be another error message from
sdap_get_generic_done().

We're not handling the case where ldap_parse_result() fails correctly and later we simply mark the request as done after checking for more LDAP_CONTROL_PAGEDRESULTS.


Fields changed

status: new => assigned

Fields changed

patch: 0 => 1

Fixed by:
- 4f2951e (master)
- 1a23caf (sssd-1-8)

component: SSSD => LDAP Provider
milestone: NEEDS_TRIAGE => SSSD 1.8.0 (LTM)
resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.8.0 (LTM)

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

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