[
https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112281#comment-14112281
]
Rakesh R commented on ZOOKEEPER-1467:
-------------------------------------
I come across this case recently. Let me try to take this JIRA ahead:).
bq.Can we use the ZK config file?
AFAIK there is no configuration file in the client side. In that case, we
should either introduce the ZooKeeper client initialization by taking
Configuration object or introduce client side configuration file. Will it be
backward compatible ?
> Server principal on client side is derived using hostname.
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-1467
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.3, 3.4.4, 3.5.0, 4.0.0
> Reporter: Laxman
> Assignee: Eugene Koontz
> Priority: Blocker
> Labels: Security, client, kerberos, sasl
> Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch
>
>
> Server principal on client side is derived using hostname.
> org.apache.zookeeper.ClientCnxn.SendThread.startConnect()
> {code}
> try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> }
> {code}
> This may have problems when admin wanted some customized principals like
> zookeeper/[email protected] where clusterid is the cluster identifier but
> not the host name.
> IMO, server principal also should be configurable as hadoop is doing.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
