[ https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941611#comment-16941611 ]
Mohammad Arshad commented on ZOOKEEPER-1467: -------------------------------------------- Thank [~sujithsimon22] for the contribution. Thanks [~eolivelli], [~enixon] for the reviews. > Make server principal configurable at client side. > -------------------------------------------------- > > Key: ZOOKEEPER-1467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1467 > Project: ZooKeeper > Issue Type: Improvement > Components: java client > Affects Versions: 3.4.3, 3.4.4, 3.5.0 > Reporter: Laxman > Assignee: Eugene Joseph Koontz > Priority: Major > Labels: Security, client, kerberos, pull-request-available, sasl > Fix For: 3.6.0, 3.5.7 > > Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > > 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/cluste...@hadoop.com 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 (v8.3.4#803005)