[ 
https://issues.apache.org/jira/browse/HADOOP-11973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550996#comment-14550996
 ] 

Hudson commented on HADOOP-11973:
---------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #7866 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/7866/])
HADOOP-11973. Ensure ZkDelegationTokenSecretManager namespace znodes get 
created with ACLs. (Gregory Chanan via asuresh) (Arun Suresh: rev 
fd3cb533d2495ea220ab2e468835a43a784d7532)
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/ZKDelegationTokenSecretManager.java
* hadoop-common-project/hadoop-common/CHANGES.txt
* 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/token/delegation/TestZKDelegationTokenSecretManager.java


> Ensure ZkDelegationTokenSecretManager namespace znodes get created with ACLs
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-11973
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11973
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 2.7.1
>
>         Attachments: HADOOP-11973.patch, HADOOP-11973v2.patch, 
> HADOOP-11973v3.patch
>
>
> I recently added an ACL Provider to the curator framework instance I pass to 
> the ZkDelegationTokenSecretManager, and notice some strangeness around ACLs.
> I set: "zk-dt-secret-manager.znodeWorkingPath" to:
> "solr/zkdtsm"
> and notice that
> /solr/zkdtsm/
> /solr/zkdtsm/ZKDTSMRoot
> do not have ACLs
> but all the znodes under /solr/zkdtsm/ZKDTSMRoot have ACLs.  From adding some 
> logging, it looks like the ACLProvider is never called for /solr/zkdtsm and 
> /solr/zkdtsm/ZKDTSMRoot.  I don't know if that's a Curator or 
> ZkDelegationTokenSecretManager issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to