Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 24562 invoked from network); 13 Sep 2005 02:54:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Sep 2005 02:54:35 -0000 Received: (qmail 12109 invoked by uid 500); 13 Sep 2005 02:54:34 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 12056 invoked by uid 500); 13 Sep 2005 02:54:33 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 12041 invoked by uid 99); 13 Sep 2005 02:54:33 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2005 19:54:32 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id F25A427B for ; Tue, 13 Sep 2005 04:54:30 +0200 (CEST) Message-ID: <566503218.1126580070959.JavaMail.jira@ajax.apache.org> Date: Tue, 13 Sep 2005 04:54:30 +0200 (CEST) From: "Alex Karasulu (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIREVE-251) case sensitivity in matching objectClass in search filter In-Reply-To: <1661117894.1126576470418.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DIREVE-251?page=comments#action_12323308 ] Alex Karasulu commented on DIREVE-251: -------------------------------------- I was sure filter value normalization was taken into account before but several things have been changing lately. However looking at the code we must make sure values in filter attribute value assertions must be normalized. Also any Assertions must normalize values in entries they compare filter values to. I thought this was done long ago but I'll recheck all the pathways. The bug is very real though .. just confirmed it. > case sensitivity in matching objectClass in search filter > --------------------------------------------------------- > > Key: DIREVE-251 > URL: http://issues.apache.org/jira/browse/DIREVE-251 > Project: Directory Server > Type: Bug > Components: protocol > Versions: 0.9.2 > Reporter: Nick Faiz > Assignee: Alex Karasulu > > ObjectClass matching in search filters is case sensitive. Is this deliberate (need to check in rfc 2254)? > OpenLDAP, on the other hand, does a case insensitive match. > A case sensitive match is not particularly helpful in this circumstance. > [nickf@little-creatures ~]$ ldapsearch -D 'uid=admin,ou=system' -h localhost -p 10389 -x -w secret -b 'ou=users,ou=system' '(&(&(cn=*)(member=cn=groupA,ou=groups,ou=system))(objectClass=inetorgperson))' > ... > # search result > search: 2 > result: 0 Success > matchedDN: ou=users,ou=system > [nickf@little-creatures ~]$ ldapsearch -D 'uid=admin,ou=system' -h localhost -p 10389 -x -w secret -b 'ou=users,ou=system' '(&(&(cn=*)(member=cn=groupA,ou=groups,ou=system))(objectClass=inetOrgPerson))' > ... > # search result > search: 2 > result: 0 Success > matchedDN: ou=users,ou=system > # numResponses: 9 > # numEntries: 8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira