[
https://issues.apache.org/jira/browse/ZOOKEEPER-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011964#comment-13011964
]
Christian Ziech commented on ZOOKEEPER-1035:
--------------------------------------------
>From a "how to fix it" point of view I don't think that I can really give
>valuable input, but from an outsider pov the quickest fix would obviously be
>to change the returned value of the IPAuthenticationProvider.isAuthenticated()
>method to true.
However this is not really helpful when having more than one
AuthenticationProvider - perhaps adding kind of ranking in between the
reliability of them would help? Only the most trustworthy
AuthenticationProvider applicable would then be taken into account to judge the
client? However I did not look into the zookeeper philosophy of those things at
all and hence don't know if it would fit.
> CREATOR_ALL_ACL does not work together with IPAuthenticationProvider
> --------------------------------------------------------------------
>
> Key: ZOOKEEPER-1035
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1035
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.1, 3.3.2
> Reporter: Christian Ziech
>
> We were trying to use the predefined ACL "Ids.CREATOR_ALL_ACL" together with
> the default ip authentication. Unfortunately it seems that this cannot work
> due to the implementation of the PrepRequestProcessor.fixupACL() method
> checking the return value of the AuthenticationProvider.isAuthenticated()
> (the IPAuthenticationProvider in our case) method.
> Unfortunately this provider always returns false which results in the
> Ids.CREATOR_ALL_ACL to be always rejected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
