[
https://issues.apache.org/jira/browse/ZOOKEEPER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved ZOOKEEPER-2331.
--------------------------------------
Resolution: Duplicate
Hello [[email protected]]. ZOOKEEPER-2139 is a prior issue that
tracks a feature enhancement to support running multiple SASL-secured ZooKeeper
clients in one process, instead of a single one controlled by a Java system
property. I recommend watching that issue if you'd like to keep track of its
progress. I'm resolving this one as a duplicate. (Please feel free to reopen
if I misunderstood.)
> Many instances of ZookeeperSaslClient in one process - every instance should
> use different jaas config section.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2331
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2331
> Project: ZooKeeper
> Issue Type: Wish
> Components: java client
> Reporter: Piotr Chmieliński
> Priority: Minor
>
> First of all I don't know if "Wish" is the best task type for it. I just want
> to ask you a question.
> Why login field in ZooKeeperSaslClient is a static one?
> https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/client/ZooKeeperSaslClient.java#L81
> I'd like to have many zookeeper clients in one process. I want each of them
> to read different section from jaas config. I know that I can specify which
> one should be read by setting system property:
> https://github.com/apache/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/client/ZooKeeperSaslClient.java#L114
> Unfortunately login field is static and it is instantiated during creation of
> first ZooKeeperSaslClient instance.
> Maybe there is some reason behind decision of making "login" static - if yes,
> could you please explain it?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
