Usage of EntryUUID index for LDAP searches

Knowledge Base Supported
, , , ,
#1

The UCR variable ldap/index/eq holds various attributes that are indexed by the ldap server. By that objetcs are searchable by these attributes.

In current UCS versions it is important that the objetcs are search- and findable by their entryUUID:

root@neuerhostname:~# univention-ldapsearch -s base entryUUID
# extended LDIF
#
# LDAPv3
# base dc=tomaten,dc=schnitzel (default) with scope baseObject
# filter: (objectclass=*)
# requesting: entryUUID
#
#tomaten.schnitzel

dn: dc=tomaten,dc=schnitzel
entryUUID: d2ee5cbe-55d0-1034-85d4-596e0af943b9

# search result
search: 3
result: 0 Success

# numResponses: 2
# numEntries: 1

# extended LDIF
#
# LDAPv3
# base dc=tomaten,dc=schnitzel (default) with scope subtree
# filter: entryUUID=d2ee5cbe-55d0-1034-85d4-596e0af943b9\# requesting: dn
#

# tomaten.schnitzel
dn: dc=tomaten,dc=schnitzel

# search result
search: 3
result: 0 Success

# numResponses: 2
# numEntries: 1

Therefore it’s important that ldap/index/eq contains entryUUID:

root@neuerhostname:~# ucr search index | grep -ic entryuuid
1

Please also see the UCS performance guide for instructions on how to generate a new slapindex if adding new attributes to ldap/index/eq, for example.

Mastodon