You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/09 01:49:38 UTC

[jira] [Resolved] (ZOOKEEPER-2709) Clarify documentation around "auth" ACL scheme

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han resolved ZOOKEEPER-2709.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.5.3
                   3.6.0

Issue resolved by pull request 182
[https://github.com/apache/zookeeper/pull/182]

> Clarify documentation around "auth" ACL scheme
> ----------------------------------------------
>
>                 Key: ZOOKEEPER-2709
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2709
>             Project: ZooKeeper
>          Issue Type: Task
>          Components: documentation
>            Reporter: Josh Elser
>            Priority: Minor
>             Fix For: 3.6.0, 3.5.3
>
>
> We recently found up in HBASE-17717 that we were incorrectly setting an ACL on our "sensitive" znodes after the output of {{getACL}} on these nodes didn't match what was expected.
> In referencing the documentation about how the {{auth}} ACL scheme was supposed to work, it was unclear if it was a ZooKeeper bug or an HBase bug. After reading some ZooKeeper code, we found that it was an HBase bug, but it would be nice to clarify the docs around this ACL scheme.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)