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

Posted to dev@zookeeper.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/02/11 12:11:20 UTC

[jira] [Commented] (ZOOKEEPER-1811) The ZooKeeperSaslClient service name principal is hardcoded to "zookeeper"

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

Hudson commented on ZOOKEEPER-1811:
-----------------------------------

SUCCESS: Integrated in ZooKeeper-trunk #2212 (See [https://builds.apache.org/job/ZooKeeper-trunk/2212/])
ZOOKEEPER-1811. The ZooKeeperSaslClient service name principal is hardcoded to "zookeeper" (Harsh J via phunt) (phunt: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1566748)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java


> The ZooKeeperSaslClient service name principal is hardcoded to "zookeeper"
> --------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1811
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1811
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.4.5
>            Reporter: Harsh J
>            Assignee: Harsh J
>             Fix For: 3.4.6, 3.5.0
>
>         Attachments: ZOOKEEPER-1811.patch
>
>
> The ClientCnxn class in ZK instantiates the ZooKeeperSaslClient with a hardcoded service name of "zookeeper". This causes all apps to fail in accessing ZK in a secure environment where the administrator has changed the principal name ZooKeeper runs as.
> The service name should be configurable.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)