[
https://issues.apache.org/jira/browse/ZOOKEEPER-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925323#action_12925323
]
Hudson commented on ZOOKEEPER-904:
----------------------------------
Integrated in ZooKeeper-trunk #981 (See
[https://hudson.apache.org/hudson/job/ZooKeeper-trunk/981/])
ZOOKEEPER-904. super digest is not actually acting as a full superuser
(Camille Fournier via mahadev)
> super digest is not actually acting as a full superuser
> -------------------------------------------------------
>
> Key: ZOOKEEPER-904
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-904
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.1
> Reporter: Camille Fournier
> Assignee: Camille Fournier
> Fix For: 3.3.2, 3.4.0
>
> Attachments: ZOOKEEPER-904-332.patch, ZOOKEEPER-904.patch
>
>
> The documentation states:
> New in 3.2: Enables a ZooKeeper ensemble administrator to access the znode
> hierarchy as a "super" user. In particular no ACL checking occurs for a user
> authenticated as super.
> However, if a super user does something like:
> zk.setACL("/", Ids.READ_ACL_UNSAFE, -1);
> the super user is now bound by read-only ACL. This is not what I would expect
> to see given the documentation. It can be fixed by moving the chec for the
> "super" authId in PrepRequestProcessor.checkACL to before the for(ACL a :
> acl) loop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
