[
https://issues.apache.org/jira/browse/ZOOKEEPER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390030#comment-14390030
]
Hongchao Deng commented on ZOOKEEPER-2153:
------------------------------------------
I said CLI because before we splited the SSL issues there is CLI suport.
I just realize that we add the following lines in
[ZooKeeperMain|https://github.com/apache/zookeeper/blob/a7b7304c413cad6ab8e1502978ed5a5192e0faf9/src/java/main/org/apache/zookeeper/ZooKeeperMain.java#L267]:
{code}
if (cl.getOption("secure") != null) {
System.setProperty(ZooKeeper.SECURE_CLIENT, "true");
System.out.println("Secure connection is enabled");
}
{code}
But we didn't expose anything to set this option. This is fine because user can
set the java property "zookeeper.client.secure".
Should we remove these lines?
4lws docs is mystic.. Let's not fix it here. We can add that to the Confluence
guide :)
> X509 Authentication Documentation
> ---------------------------------
>
> Key: ZOOKEEPER-2153
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2153
> Project: ZooKeeper
> Issue Type: Sub-task
> Reporter: Hongchao Deng
> Assignee: Ian Dimayuga
> Attachments: ZOOKEEPER-2153.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
