You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2014/11/05 12:24:33 UTC

[jira] [Created] (HADOOP-11272) Allow ZKSignerSecretProvider and ZKDelegationTokenSecretManager to use the same curator client

Arun Suresh created HADOOP-11272:
------------------------------------

             Summary: Allow ZKSignerSecretProvider and ZKDelegationTokenSecretManager to use the same curator client
                 Key: HADOOP-11272
                 URL: https://issues.apache.org/jira/browse/HADOOP-11272
             Project: Hadoop Common
          Issue Type: Bug
            Reporter: Arun Suresh


Currently the {{AuthenticationFilter}} cannot be configured to use {{ZKDelegationTokenSecretManager}} and {{ZKSignerSecretProvider}} together if the Zookeeper is a kerberized cluster. 

The zookeeper client requires certain configuration parameters to be set as SystemProperties (The issue has also been reported [here|https://issues.apache.org/jira/browse/YARN-913?focusedCommentId=14142086&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14142086]). Thus if a single process needs to use both {{ZKDelegationTokenSecretManager}} and {{ZKSignerSecretProvider}} then it should use the same client.




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