[
https://issues.apache.org/jira/browse/ZOOKEEPER-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated ZOOKEEPER-1811:
-------------------------------
Attachment: ZOOKEEPER-1811.patch
Here's a patch that makes the hardcoded name configurable (keeping the default).
> 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
> 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)
