--On Monday, August 5, 2024 10:09 AM +0000 thierryblaise@hotmail.com wrote:
Hi Quanah,
Thanks for the answer : indeed, adding the EQUALITY matching rule prior to ORDERING rule in the atttribute definition does the trick, as I can now use the filters used for ordering. However, I quickly searched for this "particularity" in the doc, the RFC, etc. and couldn't find anything about it? Is that specific to openLdap ?
However, for the index, even if "eq" index should be configured, I got this error message trying to add it : dn: olcDatabase={1}mdb,cn=config add: olcDbIndex olcDbIndex: last-modified eq
ldap_initialize( ldapi:///??base ) SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 add olcDbIndex: last-modified eq adding new entry "olcDatabase={1}mdb,cn=config" ldap_add: Object class violation (65) additional info: no objectClass attribute
I guess you have an idea what's going on?
Your modify statement is invalid. It should be:
dn: olcDatabase={1}mdb,cn=config changetype: modify add: olcDbIndex olcDbIndex: last-modified eq
--Quanah