[jira] [Commented] (ZOOKEEPER-1467) Server principal on client side is derived using hostname.

["Rakesh R (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510739#comment-14510739 ] 

Rakesh R commented on ZOOKEEPER-1467:
-------------------------------------

bq.Agree with Laxman here. I think we need to get rid of our system properties and should not be using it for configuration. Can we use the ZK config file?

Thanks [~surendrasingh] for introducing client side configuration object ZOOKEEPER-2139, which will allow to set multiple principals. I think once that is done, will come help to move ahead.

> 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/clusterid@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
(v6.3.4#6332)