Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (herse.apache.org: domain of jpyobjcdude@gmail.com
 designates 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=hqa2hXrV26vgYyO/0tOxeR6Xx9faCHs8M7WrL7brNbazDGi7SdMRC35dTtEbAFZeHq4WjR5pL0orWTss6LOtvZMyqI2o1B48Xxp8dWu97YIKevrd9LDEGS5JPRYfL5u9UBvAVnH0ikfHkSAyRs3bPxkcsXe81tKLxpkSskD2Syc=
Message-ID: <bb8e2ac20703281905p796af6caif86b83833985e39b@mail.gmail.com>
Date: Wed, 28 Mar 2007 22:05:47 -0400
From: "Tim Quinn" <jpyobjcdude@gmail.com>
To: users@directory.apache.org
Subject: Re: [ApacheDS Authorization] HELP - Server will no longer start
In-Reply-To: <a32f6b020703270718kbb2e400ifa4324a107700b11@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_41186_834470.1175133947370"
References: <bb8e2ac20703212055y18c67a08iebebe4f99270eed7@mail.gmail.com>
	 <bb8e2ac20703231519t675c9e45wc23cd7df0f781264@mail.gmail.com>
	 <a1b4a6610703240011g52a93737n1d09169eeff637b3@mail.gmail.com>
	 <a32f6b020703251626m67634b19o8dcac52fadad8516@mail.gmail.com>
	 <bb8e2ac20703261351o1088abe6p5ab10a02080a4910@mail.gmail.com>
	 <46083302.6050607@gmail.com>
	 <bb8e2ac20703261614i5f810d2yb6bfa846447ca252@mail.gmail.com>
	 <4608591B.2070308@gmail.com>
	 <bb8e2ac20703261647se2eaeao49061d724d6c9829@mail.gmail.com>
	 <a32f6b020703270718kbb2e400ifa4324a107700b11@mail.gmail.com>

------=_Part_41186_834470.1175133947370
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Glad to contribute :)

On 3/27/07, Alex Karasulu <akarasulu@apache.org> wrote:
>
> Thanks Quinn!  I'll start looking at that issue once we get 1.5.0 out.
> Perhaps we can fix this bug for 1.0.2.
>
> Alex
>
>
> On 3/26/07, Tim Quinn <jpyobjcdude@gmail.com> wrote:
> >
> > Did not realize that Apache's JIRA deployment was open to the Public :-=
)
> >
> > I'll create an account and get it into JIRA right away.
> >
> > -TQ
> >
> > On 3/26/07, Emmanuel Lecharny <elecharny@gmail.com> wrote:
> > >
> > > Tim Quinn a =E9crit :
> > >
> > > > NP. Just verified on an OOTB install of ApacheDS 1.01:
> > > >
> > > > 1) Found my derelict iBook and dusted it off ;)
> > > > 2) Installed ApacheDS (ok after sudoing installer)
> > > > 3) Started Server (ok)
> > > > 4) Connected to server using LDAP Studio (ok)
> > > > 5) Added administrativeRole attribute to entry (ok)
> > > > 6) Added a good ACI Entry (copied from working sever - ok)
> > > > 7) Removed a curly brace from the prescriptiveaci attribute (ok)
> > > > 8) Stopped and restarted server (barf)
> > > > ... Server barfed out the error as it did on my windoze box.
> > > >
> > > > :: workaround steps ::
> > > > 9) Commented out Authorization bean entry in server.xml (ok)
> > > > 10) Restarted server (ok)
> > > > 11) Fixed bad ACI Entry (ok)
> > > > 12) Restarted server (ok)
> > > > ... Worked ok - Server started without any problems.
> > > >
> > > > Thanks for your help guys and great work ;)
> > >
> > > This is definitively a bad bug !
> > >
> > > Do we have this bad ACI in JIRA ? If not, what would be really could
> > > would be to create a JIRA with the conetnt of this mail, and with the
> > > wrong ACI, so that we will be able to play with it.
> > >
> > > Thanks a lot !
> > >
> >
>

------=_Part_41186_834470.1175133947370--