Univention Bugzilla – Bug 55412
remove employeeNumber from default search filters as it is not indexed
Last modified: 2022-11-22 11:39:23 CET
(In reply to Florian Best from comment #1) > The problem could also be missing indicies. > E.g. searching in users/user by default searches in multiple properties: > also in `employeeNumber` with a search filter like > (|(employeeNumber=foo)(employeeNumber=*foo*)). But employeeNumber is only > indexed for subsearches, not equality or presence. > > management/univention-ldap/scripts/ldap_setup_index: > 260 » 'eq': UDM_PROP_ATTRS | set(( > … > 313 » )), > 314 » 'pres': UDM_PROP_ATTRS | set(( > … > 350 » )), > 351 » 'sub': set(( > … > 359 » » 'employeeNumber', > … > 379 » )), > > At least this happened in a larger customer environment. → we should remove employeeNumber from the default search attributes to gain some performance. If customers wish to use it for default search they can enable it again via: ucr set directory/manager/web/modules/users/user/properties/employeeNumber/include_in_default_search=true and add it to the equality and presence index. +++ This bug was initially created as a clone of Bug #48945 +++
employeNumber has been removed from the default search attributes. It can manually be activated via UCR if necessary (directory/manager/web/modules/users/user/properties/employeeNumber/include_in_default_search). univention-directory-manager-modules.yaml fdebc872b346 | perf(udm users): remove "employeeNumber" from default search properties in users/ univention-directory-manager-modules (15.0.13-21) fdebc872b346 | perf(udm users): remove "employeeNumber" from default search properties in users/
Verified: * Checked that the default query no longer contains the employeeNumber.
<https://errata.software-univention.de/#/?erratum=5.0x489>