[jira] [Updated] (ZOOKEEPER-1467) Make server principal configurable at client side.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated ZOOKEEPER-1467: --- Fix Version/s: 3.5.7 > 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: 1h 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)
[jira] [Updated] (ZOOKEEPER-1467) Make server principal configurable at client side.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated ZOOKEEPER-1467: --- Summary: Make server principal configurable at client side. (was: Server principal on client side is derived using hostname.) > 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 > > Attachments: ZOOKEEPER-1467.patch, ZOOKEEPER-1467.patch > > Time Spent: 1h 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)