On Wed, 2018-08-08 at 07:23 -0500, Patrick Landry wrote: > Here is the index definition: > > # memberuid, index, userRoot, ldbm database, plugins, config > dn: cn=memberuid,cn=index,cn=userRoot,cn=ldbm > database,cn=plugins,cn=config > objectClass: top > objectClass: nsIndex > nsSystemIndex: false > cn: memberuid > nsIndexType: eq > nsIndexType: pres > nsMatchingRule: caseIgnoreIA5Match Seems correct to me. > > Searches on memberuid do run much faster now so the index does seem > to be working. > > I have groups which have multivalued memberuid attributes. A search > for (memberuid=C12345) > returns several group entries but a search for (memberuid=c12345) > does not return any entries. Have you done a db2index since you made the index change above? It could still be using the original index (which is case sensitive), and we only take syntax into account as we create the index. > > > From: "William Brown" <william@xxxxxxxxxxxxxxxx> > > To: "General discussion list for the 389 Directory server project." > > <389-users@xxxxxxxxxxxxxxxxxxxxxxx> > > Sent: Tuesday, August 7, 2018 7:04:01 PM > > Subject: [389-users] Re: Attempting to make memberUID searches case > > insensitive > > > > On Tue, 2018-08-07 at 16:52 -0500, Patrick Landry wrote: > > > I am attempting to create an index which will allow searches on > > the > > > memberUID > > > attribute to be case insensitive. Using the 389-console, I > > created an > > > Additional Index > > > for memberuid and added "caseIgnoreIA5Match" as a Matching Rule. > > This > > > did not > > > produce the desired result. > > > > It would be best to see your complete index definition from > > cn=config > > for memberUID. I think something like: > > > > ldapsearch -b cn=config -D "cn=Directory Manager" ... > > '(cn=memberuid)' > > > > would suffice to find the index rules. > > > > > > > > Initially I would simply like to know if what I am asking for is > > > possible. From reading > > > the docs it seems it should be. I am able to force a > > > caseIgnoreIA5Match by using an > > > extensible match search filter. > > > > It seems like a reasonable request IMO. > > > > > > > > Once I know it is possible and that I am following the correct > > > procedure then I can > > > provide as much detail as necessary to assist in debugging. > > > > > > > > _______________________________________________ > > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to > > 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx/message/3M4FAD37YMU63GUFMKY6AYDLWIHIPUCX/ -- Sincerely, William _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx/message/WR7V5WFG7OVNFP5D4K26EFVMBJRAAP26/
