Univention Bugzilla – Bug 50252
UDM should allow to specify "+" operational attributes in object lookup()
Last modified: 2022-10-18 16:58:06 CEST
The UDM REST API needs the ldap operational attributes (+) and makes a second search after opening each object. There should be a way in UDM e.g. in lookup() or univention.admin.objects.get() to support this. This way should be used in the UDM REST API instead.
The S4-Connector also needs this feature.
And Bug #20235 as well.
Changing this might require an API change. Currently every UDM module itself defines a lookup() method instead with fixed parameters. We either need to add a parameter which allows to specify further arguments or always fetch this argument. So every existing UDM module including third party modules needs to be touched. While we are at this point we should focus on getting rid of a own implementation of lookup and always use the generic one ("lookup = object.lookup"). Alternatively we can add a hack/workaround that another LDAP search is done in the __init__ constructor but this would be very very inefficient.
Since Bug #20235 It's possible to do: univention.admin.handlers.simpleLdap._static_ldap_attributes.update({'entryCSN', 'modifyTimestamp'}) The branch git:fbest/50252-use-operational-attributes contains some performance improvements for S4-Connector and UDM REST API.