Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of elecharny@gmail.com designates
 66.249.90.183 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=OCcPXyIXPSZJtQ2J6cy4iqmt+HVJrYndQK2g3GGZhEUqD7LWtddnOyIqhWlsX0boObELTCWK4h1emilzUAeov2WsmWMkvt62ETxWCWlHNCCjIft72pWKEfy9eUGzV0jakyNkYxyUOxjmDMPNeG4vnsWWm4ju45qiBQrPpaNrq/s=
Message-ID: <d45b08f00705301243j54286159i951b6fb8d208323d@mail.gmail.com>
Date: Wed, 30 May 2007 21:43:38 +0200
From: "Emmanuel Lecharny" <elecharny@gmail.com>
Reply-To: elecharny@iktek.com
To: "Apache Directory Developers List" <dev@directory.apache.org>,
	erodriguez@apache.org
Subject: Re: [ApacheDS] Internal vs. external lookups
In-Reply-To: <568753d90705301217o6867503u1977425553370d4e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <568753d90705241516x75b659fdl3b08eba45817a4cc@mail.gmail.com>
	 <568753d90705291954w68e7b205j1306537e246763fa@mail.gmail.com>
	 <d45b08f00705300220p2fca8eefhb9f56b06f015321d@mail.gmail.com>
	 <568753d90705301217o6867503u1977425553370d4e@mail.gmail.com>

Using a special parameter and adding to to JNDI env seems a good way
to do it. If this flag is set, then it's an internal call (no need to
expose such a parameter to external users, IMHO)

Emmanuel

On 5/30/07, Enrique Rodriguez <enriquer9@gmail.com> wrote:
> On 5/30/07, Emmanuel Lecharny <elecharny@gmail.com> wrote:
> > ...
> > another solution would be to add a flag to the OperationContext which
> > is passed through the interceptors, to tell if the request is internal
> > or not.
> >
> > Those contexts have been created for such purposes.
>
> How would this flag get set when connecting via JNDI?  Today all the
> protocol providers use JNDI with CoreContextFactory.  We use
> CoreContextFactory to bind users via LDAP (external) as well as
> protocol providers (internal) so we couldn't simply have all
> CoreContextFactory initial contexts set isInternal() to "true."  We
> would need to cast to an interface to setInternal(true) or we would
> need a env parameter, such as Context.SECURITY_AUTHENTICATION =3D
> "internal".
>
> Enrique
>


--=20
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com