From users-return-3891-apmail-directory-users-archive=directory.apache.org@directory.apache.org Thu May 19 09:23:00 2011 Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04C784382 for ; Thu, 19 May 2011 09:23:00 +0000 (UTC) Received: (qmail 69648 invoked by uid 500); 19 May 2011 09:22:59 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 69622 invoked by uid 500); 19 May 2011 09:22:59 -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 69614 invoked by uid 99); 19 May 2011 09:22:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 09:22:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.220.178 as permitted sender) Received: from [209.85.220.178] (HELO mail-vx0-f178.google.com) (209.85.220.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 09:22:54 +0000 Received: by vxc11 with SMTP id 11so2148217vxc.37 for ; Thu, 19 May 2011 02:22:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=zmXPk5fVoDiFaTNZ5DTMOoWWG/UCaa0DRnruHJsgf+0=; b=Bk2s9a7zICL8rMCiLNkmZx7msTNvxHqvnj4/iIPDuQMBp1jj5NX9nBcCY8ifm/NnQE nlKsQqQ01EblVZhbMm1F7r0gCRR+rZUSvZcbMLXvj0R5Q+A1rdpzu/EVrcJYmXYrU38n gkDuqBb+sflbi51RgO+fvfDcs0kIZrZOU+P14= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=V1dmZ62XznpXq8TV7dWbs+YI2CK+1NJWMJsibAC2zZJtNwUHBRNguT5pqGkNE82ke0 oXlfizE/fY+hWhTNE3AVUk8v1W+ZjjloKPETcHAq/HkhKQoMf5aosyLpgX2gpIdgW61/ AviVaPuPIUDiGuA4BFlwDEXpHGjqDSz/l8IDY= MIME-Version: 1.0 Received: by 10.52.73.194 with SMTP id n2mr1648262vdv.307.1305796953730; Thu, 19 May 2011 02:22:33 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.52.184.35 with HTTP; Thu, 19 May 2011 02:22:33 -0700 (PDT) In-Reply-To: <4DD4D7BA.4060104@gmail.com> References: <4DD4D237.2000905@papercut.com> <4DD4D7BA.4060104@gmail.com> Date: Thu, 19 May 2011 14:52:33 +0530 X-Google-Sender-Auth: j-nwBCnQUl5ysRAdrRn2QSqVzi8 Message-ID: Subject: Re: Custom LDAP partition and root/baseless searches From: Kiran Ayyagari To: users@directory.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, May 19, 2011 at 2:11 PM, Emmanuel Lecharny wr= ote: > On 5/19/11 10:17 AM, Matt Doran wrote: >> >> Hi there, >> >> I'm using a *very* basic custom LDAP partition in Apache DS (it's an old= er >> version 1.5.5, because at the time of writing this was the best version = to >> get a custom LDAP partition working). >> >> We are using this embedded in our product to mimic a "real" LDAP server >> for a very specific purpose (mainly around authentication and a very bas= ic >> user attribute lookup). >> >> One of the services that is interacting with us now is performing a root >> search (I'm not sure if that's the right term). =A0 But basically they a= re now >> doing a search without providing an search base DN (i.e. the search base= is >> empty ""). =A0See the attached image for a part of the wireshark dump fo= r this >> search. >> >> The problem we're having is that when we receive this search, the >> "search()" method of our custom LDAP partition is not being called. =A0I >> haven't been able to find the answer in your docs (probably because I do= n't >> know the terminology to search for :) >> >> So I'm wondering how we can hook into these baseless searches? =A0 Is th= ere >> a way to set-up the partition so we will be passed these search requests= ? >> >> Is there a way to "plug-in" to handle these searches and modify them or >> direct them in some way to our custom partition. > > 'Root' searches are supposed to work well. The way it works is that it lo= oks > into all the naming contexts present in the RootDSE entry. I guess that y= ou > have such a naming context present, otherwise you would not be able to do > any search in your specific partition. > > It may be a bug in 1.5.5. I suggest you quickly do a test with the latest > version (1.5.7) to see if the problem still exists (we fixed a large numb= er > of bugs between 1.5.5. and 1.5.7). If the proble still exists, then it's > most certainly a bug and deserves a JIRA. > this was fixed in 1.5.7, and if you migrate to 1.5.7 then it will work. > > -- > Regards, > Cordialement, > Emmanuel L=E9charny > www.iktek.com > > --=20 Kiran Ayyagari