You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Tim Quinn <jp...@gmail.com> on 2007/03/22 04:55:25 UTC
[ApacheDS Authorization] HELP - Server will no longer start
I've been playing around with ACI and am getting the following barf on
server startup (which fails):
2007-03-21 23:51:18,375 [Thread-0] WARN 191 TupleCache.subentryAdded -
ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
java.text.ParseException: Parser failure on ACIItem:
{
identificationTag "enableSearchForAllUsers",
precedence 14,
....
}
Antlr exception trace:
unexpected token: name
at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
ACIItemParser.java:128)
at org.apache.directory.server.core.authz.TupleCache.subentryAdded(
TupleCache.java:186)
at org.apache.directory.server.core.authz.TupleCache.initialize(
TupleCache.java:139)
at org.apache.directory.server.core.authz.TupleCache.<init>(
TupleCache.java:101)
at org.apache.directory.server.core.authz.AuthorizationService.init(
AuthorizationService.java:173)
at
org.apache.directory.server.core.interceptor.InterceptorChain.register0(
InterceptorChain.java:436)
at
org.apache.directory.server.core.interceptor.InterceptorChain.register(
InterceptorChain.java:395)
at
org.apache.directory.server.core.interceptor.InterceptorChain.init(
InterceptorChain.java:260)
...
~end~
I have tried turning off accessControlEnabled to see if that allows me to
start the server but it does not. How to I fix this entry?
I seem to be snookered at the moment :(
Thanks,
JsD
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
On 3/21/07, Tim Quinn <jp...@gmail.com> wrote:
>
> I've been playing around with ACI and am getting the following barf on
> server startup (which fails):
>
> 2007-03-21 23:51:18,375 [Thread-0] WARN 191 TupleCache.subentryAdded -
> ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> java.text.ParseException: Parser failure on ACIItem:
> {
> identificationTag "enableSearchForAllUsers",
> precedence 14,
> ....
> }
> Antlr exception trace:
> unexpected token: name
> at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> ACIItemParser.java:128)
> at org.apache.directory.server.core.authz.TupleCache.subentryAdded
> (TupleCache.java:186)
> at org.apache.directory.server.core.authz.TupleCache.initialize (
> TupleCache.java:139)
> at org.apache.directory.server.core.authz.TupleCache.<init>(
> TupleCache.java:101)
> at
> org.apache.directory.server.core.authz.AuthorizationService.init(
> AuthorizationService.java :173)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain.register0(
> InterceptorChain.java:436)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain.register(
> InterceptorChain.java :395)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain.init(
> InterceptorChain.java:260)
> ...
>
> ~end~
>
> I have tried turning off accessControlEnabled to see if that allows me to
> start the server but it does not. How to I fix this entry?
>
> I seem to be snookered at the moment :(
>
> Thanks,
> JsD
>
Resolved =^o
Fix required to get around this ugly situation:
In Config.xml, comment out AuthorizationService Interceptor definition.
~snip~
<!--bean class="
org.apache.directory.server.core.configuration.MutableInterceptorConfiguration
">
<property name="name" value="authorizationService" />
<property name="interceptor">
<bean class="
org.apache.directory.server.core.authz.AuthorizationService" />
</property>
</bean-->
~/snip~
Regards,
JsD
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
Glad to contribute :)
On 3/27/07, Alex Karasulu <ak...@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 <jp...@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 <el...@gmail.com> wrote:
> > >
> > > Tim Quinn a écrit :
> > >
> > > > 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 !
> > >
> >
>
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Alex Karasulu <ak...@apache.org>.
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 <jp...@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 <el...@gmail.com> wrote:
> >
> > Tim Quinn a écrit :
> >
> > > 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 !
> >
>
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Emmanuel Lecharny <el...@gmail.com>.
Tim Quinn a écrit :
> Did not realize that Apache's JIRA deployment was open to the Public :-)
eh, do you think that developpers are finding all the bugs themselves ?
;) This is Apache, this is not Perfection...
>
> I'll create an account and get it into JIRA right away.
Great !
Emmanuel
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
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 <el...@gmail.com> wrote:
>
> Tim Quinn a écrit :
>
> > 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 !
>
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Emmanuel Lecharny <el...@gmail.com>.
Tim Quinn a écrit :
> 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 !
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
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 ;)
-TQ
On 3/26/07, Emmanuel Lecharny <el...@gmail.com> wrote:
>
> Tim Quinn a écrit :
>
> > Sounds like that is the case...
> >
> > I will be building up an test case on an OOTB installation.
> >
> > I created the bad ACIItem using an LDLAP Studio.
>
> Thanks a lot Quin, and sorry for the NPE... NPE should never occurs even
> if the user feed the server with bad data. The test case will help us a
> lot to fix the issue !
>
> Emmanuel
>
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Emmanuel Lecharny <el...@gmail.com>.
Tim Quinn a écrit :
> Sounds like that is the case...
>
> I will be building up an test case on an OOTB installation.
>
> I created the bad ACIItem using an LDLAP Studio.
Thanks a lot Quin, and sorry for the NPE... NPE should never occurs even
if the user feed the server with bad data. The test case will help us a
lot to fix the issue !
Emmanuel
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
Sounds like that is the case...
I will be building up an test case on an OOTB installation.
I created the bad ACIItem using an LDLAP Studio.
-TQ
On 3/25/07, Alex Karasulu <ak...@apache.org> wrote:
>
> The interceptor's tuple case may still be initialized even though the
> interceptor is really not doing any work. The problem is perhaps due to
> it's encountering a bad ACIITem and blowing chunks.
>
> Alex
>
>
> On 3/24/07, Ersin Er <er...@gmail.com> wrote:
> >
> > On 3/24/07, Tim Quinn <jp...@gmail.com> wrote:
> > >
> > > >
> > > > As it's currently implemented if accessControlEnabled is set to
> false
> > > > authz.AuthorizationService does not make any authorization
> operations
> > > and
> > > > just bypasses the requests (and responses). So you rproblem may be
> > > related
> > > > to something different.
> > > >
> > >
> > >
> > > I just verified again. By removing just the last close curly brace,
> the
> > > start fails with the following
> > >
> > > ~snip~
> > > 2007-03-23 18:12:13,062 [Thread-0] WARN 191 TupleCache.subentryAdded-
> > > ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> > > java.text.ParseException: Parser failure on ACIItem:
> > > {
> > > identificationTag "enableSearchForADSGenReader_ACI",
> > > precedence 10,
> > > authenticationLevel none,
> > > itemOrUserFirst userFirst:
> > > {
> > > userClasses
> > > {
> > > name { "uid=ADSGenReader,ou=admin,ou=system" }
> > > },
> > > userPermissions
> > > {
> > > {
> > > protectedItems { entry, allUserAttributeTypesAndValues },
> > > grantsAndDenials { grantRead, grantBrowse, grantReturnDN,
> > > grantCompare, grantFilterMatch,
> > > grantDiscloseOnError }
> > > },
> > > {
> > > protectedItems { attributeType { userPassword } },
> > > grantsAndDenials { denyRead, denyCompare, denyFilterMatch }
> > > }
> > > }
> > > }
> > > Antlr exception trace:
> > > expecting CLOSE_CURLY, found 'null'
> > > at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> > > ACIItemParser.java:128)
> > > at
> > org.apache.directory.server.core.authz.TupleCache.subentryAdded
> > > (
> > > TupleCache.java:186)
> > > ~/snip~
> > >
> > > This error shows up and the server fails to start regardless of the
> > > accessControlEnabled setting in config.xml.
> > >
> > > If you want, I can build up a test case on a OOTB fresh installation
> to
> > > make
> > > sure that it is not related to some of my own jars.
> >
> >
> > Test cases are always greatly appreciated :-)
> >
> > ..TQ
> > >
> >
> >
> >
> > --
> > Ersin
> >
>
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Alex Karasulu <ak...@apache.org>.
The interceptor's tuple case may still be initialized even though the
interceptor is really not doing any work. The problem is perhaps due to
it's encountering a bad ACIITem and blowing chunks.
Alex
On 3/24/07, Ersin Er <er...@gmail.com> wrote:
>
> On 3/24/07, Tim Quinn <jp...@gmail.com> wrote:
> >
> > >
> > > As it's currently implemented if accessControlEnabled is set to false
> > > authz.AuthorizationService does not make any authorization operations
> > and
> > > just bypasses the requests (and responses). So you rproblem may be
> > related
> > > to something different.
> > >
> >
> >
> > I just verified again. By removing just the last close curly brace, the
> > start fails with the following
> >
> > ~snip~
> > 2007-03-23 18:12:13,062 [Thread-0] WARN 191 TupleCache.subentryAdded -
> > ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> > java.text.ParseException: Parser failure on ACIItem:
> > {
> > identificationTag "enableSearchForADSGenReader_ACI",
> > precedence 10,
> > authenticationLevel none,
> > itemOrUserFirst userFirst:
> > {
> > userClasses
> > {
> > name { "uid=ADSGenReader,ou=admin,ou=system" }
> > },
> > userPermissions
> > {
> > {
> > protectedItems { entry, allUserAttributeTypesAndValues },
> > grantsAndDenials { grantRead, grantBrowse, grantReturnDN,
> > grantCompare, grantFilterMatch,
> > grantDiscloseOnError }
> > },
> > {
> > protectedItems { attributeType { userPassword } },
> > grantsAndDenials { denyRead, denyCompare, denyFilterMatch }
> > }
> > }
> > }
> > Antlr exception trace:
> > expecting CLOSE_CURLY, found 'null'
> > at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> > ACIItemParser.java:128)
> > at
> org.apache.directory.server.core.authz.TupleCache.subentryAdded
> > (
> > TupleCache.java:186)
> > ~/snip~
> >
> > This error shows up and the server fails to start regardless of the
> > accessControlEnabled setting in config.xml.
> >
> > If you want, I can build up a test case on a OOTB fresh installation to
> > make
> > sure that it is not related to some of my own jars.
>
>
> Test cases are always greatly appreciated :-)
>
> ..TQ
> >
>
>
>
> --
> Ersin
>
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Ersin Er <er...@gmail.com>.
On 3/24/07, Tim Quinn <jp...@gmail.com> wrote:
>
> >
> > As it's currently implemented if accessControlEnabled is set to false
> > authz.AuthorizationService does not make any authorization operations
> and
> > just bypasses the requests (and responses). So you rproblem may be
> related
> > to something different.
> >
>
>
> I just verified again. By removing just the last close curly brace, the
> start fails with the following
>
> ~snip~
> 2007-03-23 18:12:13,062 [Thread-0] WARN 191 TupleCache.subentryAdded -
> ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> java.text.ParseException: Parser failure on ACIItem:
> {
> identificationTag "enableSearchForADSGenReader_ACI",
> precedence 10,
> authenticationLevel none,
> itemOrUserFirst userFirst:
> {
> userClasses
> {
> name { "uid=ADSGenReader,ou=admin,ou=system" }
> },
> userPermissions
> {
> {
> protectedItems { entry, allUserAttributeTypesAndValues },
> grantsAndDenials { grantRead, grantBrowse, grantReturnDN,
> grantCompare, grantFilterMatch,
> grantDiscloseOnError }
> },
> {
> protectedItems { attributeType { userPassword } },
> grantsAndDenials { denyRead, denyCompare, denyFilterMatch }
> }
> }
> }
> Antlr exception trace:
> expecting CLOSE_CURLY, found 'null'
> at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> ACIItemParser.java:128)
> at org.apache.directory.server.core.authz.TupleCache.subentryAdded
> (
> TupleCache.java:186)
> ~/snip~
>
> This error shows up and the server fails to start regardless of the
> accessControlEnabled setting in config.xml.
>
> If you want, I can build up a test case on a OOTB fresh installation to
> make
> sure that it is not related to some of my own jars.
Test cases are always greatly appreciated :-)
..TQ
>
--
Ersin
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
>
> As it's currently implemented if accessControlEnabled is set to false
> authz.AuthorizationService does not make any authorization operations and
> just bypasses the requests (and responses). So you rproblem may be related
> to something different.
>
I just verified again. By removing just the last close curly brace, the
start fails with the following
~snip~
2007-03-23 18:12:13,062 [Thread-0] WARN 191 TupleCache.subentryAdded -
ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
java.text.ParseException: Parser failure on ACIItem:
{
identificationTag "enableSearchForADSGenReader_ACI",
precedence 10,
authenticationLevel none,
itemOrUserFirst userFirst:
{
userClasses
{
name { "uid=ADSGenReader,ou=admin,ou=system" }
},
userPermissions
{
{
protectedItems { entry, allUserAttributeTypesAndValues },
grantsAndDenials { grantRead, grantBrowse, grantReturnDN,
grantCompare, grantFilterMatch,
grantDiscloseOnError }
},
{
protectedItems { attributeType { userPassword } },
grantsAndDenials { denyRead, denyCompare, denyFilterMatch }
}
}
}
Antlr exception trace:
expecting CLOSE_CURLY, found 'null'
at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
ACIItemParser.java:128)
at org.apache.directory.server.core.authz.TupleCache.subentryAdded(
TupleCache.java:186)
~/snip~
This error shows up and the server fails to start regardless of the
accessControlEnabled setting in config.xml.
If you want, I can build up a test case on a OOTB fresh installation to make
sure that it is not related to some of my own jars.
..TQ
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Ersin Er <er...@gmail.com>.
On 3/24/07, Tim Quinn <jp...@gmail.com> wrote:
>
> On 3/23/07, Ersin Er <er...@gmail.com> wrote:
> >
> > Hi,
> >
> > Can you please post the ACIItem you have written?
> >
> > On 3/22/07, Tim Quinn <jp...@gmail.com> wrote:
> > >
> > > I've been playing around with ACI and am getting the following barf on
> > > server startup (which fails):
> > >
> > > 2007-03-21 23:51:18,375 [Thread-0] WARN 191 TupleCache.subentryAdded-
> > > ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> > > java.text.ParseException: Parser failure on ACIItem:
> > > {
> > > identificationTag "enableSearchForAllUsers",
> > > precedence 14,
> > > ....
> > > }
> > > Antlr exception trace:
> > > unexpected token: name
> > > at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> > > ACIItemParser.java:128)
> > > at
> > org.apache.directory.server.core.authz.TupleCache.subentryAdded
> > > (
> > > TupleCache.java:186)
> > > at
> org.apache.directory.server.core.authz.TupleCache.initialize(
> > > TupleCache.java:139)
> > > at org.apache.directory.server.core.authz.TupleCache.<init>(
> > > TupleCache.java:101)
> > > at
> > > org.apache.directory.server.core.authz.AuthorizationService.init(
> > > AuthorizationService.java:173)
> > > at
> > >
> org.apache.directory.server.core.interceptor.InterceptorChain.register0(
> > > InterceptorChain.java:436)
> > > at
> > > org.apache.directory.server.core.interceptor.InterceptorChain.register
> (
> > > InterceptorChain.java:395)
> > > at
> > > org.apache.directory.server.core.interceptor.InterceptorChain.init(
> > > InterceptorChain.java:260)
> > > ...
> > >
> > > ~end~
> > >
> > > I have tried turning off accessControlEnabled to see if that allows me
> > to
> > > start the server but it does not. How to I fix this entry?
> > >
> > > I seem to be snookered at the moment :(
> > >
> > > Thanks,
> > > JsD
> > >
> >
> >
> >
> > --
> > Ersin
> >
>
> Hello Ersin,
>
> The syntax that I had contained a trivial error that I have since fixed.
> The
> main problem I had was that I could not bring the server back up to fix
> this
> syntax error. This caused a bit of a scare for me.
>
> Since I know that others will experience the same, maybe there should be a
> patch put into authz.AuthorizationService to detect the
> accessControlEnabled
> setting in the server config.xml and not completely block the server
> startup
> if accessControlEnabled is set to false...?
As it's currently implemented if accessControlEnabled is set to false
authz.AuthorizationService does not make any authorization operations and
just bypasses the requests (and responses). So you rproblem may be related
to something different.
..JsD
>
--
Ersin
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Tim Quinn <jp...@gmail.com>.
On 3/23/07, Ersin Er <er...@gmail.com> wrote:
>
> Hi,
>
> Can you please post the ACIItem you have written?
>
> On 3/22/07, Tim Quinn <jp...@gmail.com> wrote:
> >
> > I've been playing around with ACI and am getting the following barf on
> > server startup (which fails):
> >
> > 2007-03-21 23:51:18,375 [Thread-0] WARN 191 TupleCache.subentryAdded -
> > ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> > java.text.ParseException: Parser failure on ACIItem:
> > {
> > identificationTag "enableSearchForAllUsers",
> > precedence 14,
> > ....
> > }
> > Antlr exception trace:
> > unexpected token: name
> > at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> > ACIItemParser.java:128)
> > at
> org.apache.directory.server.core.authz.TupleCache.subentryAdded
> > (
> > TupleCache.java:186)
> > at org.apache.directory.server.core.authz.TupleCache.initialize(
> > TupleCache.java:139)
> > at org.apache.directory.server.core.authz.TupleCache.<init>(
> > TupleCache.java:101)
> > at
> > org.apache.directory.server.core.authz.AuthorizationService.init(
> > AuthorizationService.java:173)
> > at
> > org.apache.directory.server.core.interceptor.InterceptorChain.register0(
> > InterceptorChain.java:436)
> > at
> > org.apache.directory.server.core.interceptor.InterceptorChain.register(
> > InterceptorChain.java:395)
> > at
> > org.apache.directory.server.core.interceptor.InterceptorChain.init(
> > InterceptorChain.java:260)
> > ...
> >
> > ~end~
> >
> > I have tried turning off accessControlEnabled to see if that allows me
> to
> > start the server but it does not. How to I fix this entry?
> >
> > I seem to be snookered at the moment :(
> >
> > Thanks,
> > JsD
> >
>
>
>
> --
> Ersin
>
Hello Ersin,
The syntax that I had contained a trivial error that I have since fixed. The
main problem I had was that I could not bring the server back up to fix this
syntax error. This caused a bit of a scare for me.
Since I know that others will experience the same, maybe there should be a
patch put into authz.AuthorizationService to detect the accessControlEnabled
setting in the server config.xml and not completely block the server startup
if accessControlEnabled is set to false...?
..JsD
Re: [ApacheDS Authorization] HELP - Server will no longer start
Posted by Ersin Er <er...@gmail.com>.
Hi,
Can you please post the ACIItem you have written?
On 3/22/07, Tim Quinn <jp...@gmail.com> wrote:
>
> I've been playing around with ACI and am getting the following barf on
> server startup (which fails):
>
> 2007-03-21 23:51:18,375 [Thread-0] WARN 191 TupleCache.subentryAdded -
> ACIItem parser failure on 'null'. Cannnot add ACITuples to TupleCache.
> java.text.ParseException: Parser failure on ACIItem:
> {
> identificationTag "enableSearchForAllUsers",
> precedence 14,
> ....
> }
> Antlr exception trace:
> unexpected token: name
> at org.apache.directory.shared.ldap.aci.ACIItemParser.parse(
> ACIItemParser.java:128)
> at org.apache.directory.server.core.authz.TupleCache.subentryAdded
> (
> TupleCache.java:186)
> at org.apache.directory.server.core.authz.TupleCache.initialize(
> TupleCache.java:139)
> at org.apache.directory.server.core.authz.TupleCache.<init>(
> TupleCache.java:101)
> at
> org.apache.directory.server.core.authz.AuthorizationService.init(
> AuthorizationService.java:173)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain.register0(
> InterceptorChain.java:436)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain.register(
> InterceptorChain.java:395)
> at
> org.apache.directory.server.core.interceptor.InterceptorChain.init(
> InterceptorChain.java:260)
> ...
>
> ~end~
>
> I have tried turning off accessControlEnabled to see if that allows me to
> start the server but it does not. How to I fix this entry?
>
> I seem to be snookered at the moment :(
>
> Thanks,
> JsD
>
--
Ersin