Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 6535 invoked from network); 8 Oct 2007 14:06:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2007 14:06:55 -0000 Received: (qmail 12444 invoked by uid 500); 8 Oct 2007 14:06:43 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 12348 invoked by uid 500); 8 Oct 2007 14:06:43 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 12337 invoked by uid 99); 8 Oct 2007 14:06:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2007 07:06:43 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [194.25.216.40] (HELO scrat.ecrmforce.biz) (194.25.216.40) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2007 14:06:46 +0000 Received: from [172.16.156.161] (unknown [172.16.156.161]) by scrat.ecrmforce.biz (Postfix) with ESMTP id 90DA977C68 for ; Mon, 8 Oct 2007 16:06:10 +0200 (CEST) Message-ID: <470A3930.9070809@webunity.de> Date: Mon, 08 Oct 2007 16:05:36 +0200 From: Markus Pohle User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: [ApacheDS 1.5.1] unable to search for uniqueMember References: <20071005190330.dojpsfu4fug0koo4@nemo.granus-werkstatt.de> <470A2051.3080407@webunity.de> <470A2D63.5090000@webunity.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Ok, i see! I do understand that ApacheDS 1.5.0 was buggy and therefor version 1.5.1 was released which is stricter regarding search requests. Is there a way to do that kind of search with a different way within Directory Studio? I ask that because I have to handle a large amount of LDAP information where I often need to search for such a think like (uniqueMember=uid=g.kelly*) More and more often I realize that LDAP is not that "Lightweight" its name implies :-) Sorry for all my questions Markus Emmanuel Lecharny schrieb: > Hi, > > 1.5.0 was buggy, so we released 1.5.1 > > 1.5.1 is much more strict regarding search requests, and this is why > what was possible with the old version is not anymore allowad. > > Again, doing a seach with (uniqueMember=uid*) is _not_ allowed by the > LDAP specification. At best, you should get an empty list. > > Substring search are valid for strings. A DN is not as string. > > On 10/8/07, Markus Pohle wrote: >> Hi Emmanuel, >> >> nope sorry - that doesn't make it clearer for me - seems I am too >> dump...?!??! >> >> Why I am able to do such a search for uniqueMember in an ApacheDS >> Version 1.5.0 and within the snapshot build that Alex made for me some >> weeks ago? >> >> I am totally confused and apologize for that! >> >> Markus >> >> Emmanuel Lecharny schrieb: >>> Hi Markus, >>> >>> the UniqueMember attributeType is a distinguishedName, which is not a >>> string. Doing a substring search on a non-string object is not >>> possible (in fact, it should be treated as undefined - see RFC 4511, >>> par. 4.5.1.7) >>> >>> You cannot get any result with such a filter : >>> (uniqueMember=uid=g.kelly*) >>> >>> Nor can you with : >>> (ObjectClass=orga*) >>> >>> Currently, you will simply get a NPE, which will translate to an >>> Unexpected Exception on the client side. >>> >>> I'm currently investigating what we should return, and I think the >>> client should receive an empty result instead of an exception. >>> >>> I hope it's clear enough >>> >>> Emmanuel >>> > >