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 (athena.apache.org: domain of elecharny@gmail.com
 designates 209.85.128.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=NQ3/6/QFnmRGr80VhOBCoJP2FZYOAKPaamGsHDHO4GZKJWRgq6/BW3jKp6RKRNCRha
         oAh3vBzwlGiw9Rw6pi6ZfvETBuPiSt1DdNsSFVxHctiR+gMg7+rY9il08IJM6uOcAj9a
         ikE6dy2ZliNOVf/9AgoCgX5WWgdPp6dH3rbTs=
Message-ID: <4878AD04.4060802@gmail.com>
Date: Sat, 12 Jul 2008 15:09:24 +0200
From: Emmanuel Lecharny <elecharny@gmail.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [bb] MiscITest failure, take 2
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

I still have failures on MiscITest, on both testDisableAnonymousBinds() 
and testEnableAnonymousBindsOnRootDSE() unit tests.

The reason why we have some failure is because we have disabled 
anonymous bind on the server. The big problem is that it's now handled 
in the Bind handler, which is called while creating the context.

The big problem is that as soon as we are not allowed to do an anonymous 
bind, then we can't anymore create a context. Then any kind of following 
operation will fail, and this is the reason why the tests are failing.

InitialContextCreation should not try to bind the user, unless we are 
not asking for an Anonymous Bind. We hould just create a context, and 
return it to the user. As soon as e will try to do a search, if the 
Anonymous state is not allowed, then it will get an exception.

In fact, the Anonymous bind is not a bind at all, it's just a state we 
get into as soon as we open a session on the server. Until we close the 
session (or it is closed buy the server itself), the user is either in 
Anonymous state or in authenticated state. Switching from one state to 
the other requires either a user action (a Bind with another mechanism, 
an Unbind) or a server action (authent revocation if the authent is 
based on certificate, and the certificate is revoqued or expire during a 
session).

We have to review all the BigBang authentication mechanism as fast as 
possible.

I'm disabling those two tests.

Thanks !