[
https://issues.apache.org/jira/browse/ZOOKEEPER-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624067#comment-13624067
]
Arpit Gupta commented on ZOOKEEPER-1685:
----------------------------------------
I think we should make it configurable which principal to use so both the
server and the client can use the same when authenticating.
> Zookeeper client hard codes the server principal to zookeeper
> -------------------------------------------------------------
>
> Key: ZOOKEEPER-1685
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1685
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.4.5
> Reporter: Arpit Gupta
>
> Noticed this while debugging a secure deploy. The server was started with the
> principal zk/_HOST
> When a client tried to connect to this it tried to setup a secure connection
> to server zookeeper/_HOST and failed authentication.
> In ClientCnxn.java
> {code}
> try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> } catch (LoginException e) {
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
