#2666 sssd with ldap backend throws error domain log
Closed: Fixed None Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1227685

Description of problem:
sssd with ldap backend throws error domain log.

Version-Release number of selected component (if applicable):
sssd-1.12.4-42.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Setup sssd using ldap backend. Set "debug_level = 10"
2. Try user lookup. Lookup/Auth works fine.
3. sssd throws following error in domain log

(Fri Jun  3 15:17:32 2016) [sssd[be[LDAP]]] [sdap_attrs_get_sid_str] (0x1000):
No [objectSID] attribute. [0][Success]
(Fri Jun  3 15:17:32 2016) [sssd[be[LDAP]]] [sdap_save_user] (0x4000):
objectSID: not available for user
(Fri Jun  3 15:17:32 2016) [sssd[be[LDAP]]] [sdap_save_user] (0x0080): Failed
to retrieve UUID [22][Invalid argument].
(Fri Jun  3 15:17:32 2016) [sssd[be[LDAP]]] [sdap_get_primary_name] (0x0400):
Processing object shadowuser1
(Fri Jun  3 15:17:32 2016) [sssd[be[LDAP]]] [sdap_save_user] (0x0400):
Processing user shadowuser1

Actual results:
sssd throws following error in domain log

Expected results:
No error should occur, as lookup/Auth works fine.

The errors come from sysdb_handle_original_uuid that checks if any of its input parameters are NULL. But with a plain LDAP back end, the UUID parameters are not set, so the check will error out.

The only visible effect is noise in the logs..

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

milestone: NEEDS_TRIAGE => SSSD 1.13 alpha
status: assigned => new

Fields changed

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.13 alpha

3 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/3707

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