Bug 35975 - LDAP_ConnectionError: Bad search filter: during loading of user
LDAP_ConnectionError: Bad search filter: during loading of user
Status: CLOSED DUPLICATE of bug 35953
Product: UCS
Classification: Unclassified
Component: UMC - Domain management (Generic)
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-22 11:30 CEST by Florian Best
Modified: 2015-08-31 08:26 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, External feedback, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2014-09-22 11:30:42 CEST
Traceback:
  File "/usr/lib/pymodules/python2.6/notifier/threads.py", line 82, in _run
    tmp = self._function()
  File "/usr/lib/pymodules/python2.6/notifier/__init__.py", line 104, in __call__
    return self._function( *tmp, **self._kwargs )
  File
"/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/__init__.py", line
450, in _thread
    obj = module.get( ldap_dn )
  File
"/usr/lib/pymodules/python2.6/univention/management/console/modules/udm/udm_ldap.py", line
213, in wrapper_func
    raise LDAP_ConnectionError( str( e ) )

LDAP_ConnectionError: Bad search filter

Remark:
This same issue happened but was resolved in the last update.  Modification of this user
profile has caused the same issue to reappear.  Error happens simply selecting user OR
using LDAP Directory | Users

The error handling in the code seems also to be wrong:
 453 »   »   »   »   »   obj = module.get( ldap_dn )
 454 »   »   »   »   »   if obj:
…
 470 »   »   »   »   »   »   result.append( props )
 471 »   »   »   »   »   else:
 472 »   »   »   »   »   »   MODULE.process( 'The LDAP object for the LDAP DN %s could not be found' % ldap_dn )
 473 »   »   »   return result
Comment 1 Alexander Kläser univentionstaff 2014-09-24 15:10:37 CEST
@Drees: Might this be related to Bug 29231 and Bug 34246?
Comment 2 Florian Best univentionstaff 2014-12-02 16:49:58 CET
I would like to know how to reproduce this. Simply opening a not existing user does not work. Also opening a moved user does not work.
We know that this is the udm/get command. From the remark we know that it happens for a user object.
Comment 3 Florian Best univentionstaff 2014-12-02 16:59:51 CET
(off topic) Just a guess, would be interesting to know:
### (→ base = 'users')
modules = udm_modules.objectType(None, ldap_connection, ldap_dn, module_base=base)
return UDM_Module(modules[0])
####
→ If multiple UDM modules identify the object as its own the "modules" list could e.g. contain "users/self" and "users/user" or some module from an app vendor.
Comment 4 Florian Best univentionstaff 2014-12-02 17:13:32 CET
Ahh, got it. This was ticket #2014091821000144 which is 3.2-3 errata206 (Borgfeld). This error was already fixed in Bug #35953 which is errata 237.

http://errata.univention.de/ucs/3.2/237.html

*** This bug has been marked as a duplicate of bug 35953 ***