[jira] [Updated] (ZOOKEEPER-2314) Improvements to SASL

2017-03-13 Thread Michael Han (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Han updated ZOOKEEPER-2314:
---
Fix Version/s: (was: 3.4.11)
   (was: 3.5.3)
   3.5.4

> Improvements to SASL
> 
>
> Key: ZOOKEEPER-2314
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Flavio Junqueira
>Assignee: Flavio Junqueira
> Fix For: 3.5.4, 3.6.0
>
>
> Points that occur to me right now:
> # The login object in ZooKeeperSaslClient is static, which means that if you 
> try to create another client for tests, the login object will be the first 
> one you've set for all runs. I've experienced this with 3.4.6.
> # There are a number of properties spread across the code that do not appear 
> in the docs. For example, zookeeper.allowSaslFailedClients isn't documented 
> afaict.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (ZOOKEEPER-2314) Improvements to SASL

2017-03-06 Thread Michael Han (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Han updated ZOOKEEPER-2314:
---
Priority: Major  (was: Blocker)

> Improvements to SASL
> 
>
> Key: ZOOKEEPER-2314
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Flavio Junqueira
>Assignee: Flavio Junqueira
> Fix For: 3.5.3, 3.6.0, 3.4.11
>
>
> Points that occur to me right now:
> # The login object in ZooKeeperSaslClient is static, which means that if you 
> try to create another client for tests, the login object will be the first 
> one you've set for all runs. I've experienced this with 3.4.6.
> # There are a number of properties spread across the code that do not appear 
> in the docs. For example, zookeeper.allowSaslFailedClients isn't documented 
> afaict.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (ZOOKEEPER-2314) Improvements to SASL

2016-08-16 Thread Rakesh R (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R updated ZOOKEEPER-2314:

Fix Version/s: (was: 3.4.9)
   3.4.10

> Improvements to SASL
> 
>
> Key: ZOOKEEPER-2314
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Flavio Junqueira
>Assignee: Flavio Junqueira
>Priority: Blocker
> Fix For: 3.5.3, 3.6.0, 3.4.10
>
>
> Points that occur to me right now:
> # The login object in ZooKeeperSaslClient is static, which means that if you 
> try to create another client for tests, the login object will be the first 
> one you've set for all runs. I've experienced this with 3.4.6.
> # There are a number of properties spread across the code that do not appear 
> in the docs. For example, zookeeper.allowSaslFailedClients isn't documented 
> afaict.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ZOOKEEPER-2314) Improvements to SASL

2016-06-21 Thread Chris Nauroth (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated ZOOKEEPER-2314:
-
Fix Version/s: (was: 3.5.2)
   3.5.3

> Improvements to SASL
> 
>
> Key: ZOOKEEPER-2314
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Flavio Junqueira
>Assignee: Flavio Junqueira
>Priority: Blocker
> Fix For: 3.4.9, 3.6.0, 3.5.3
>
>
> Points that occur to me right now:
> # The login object in ZooKeeperSaslClient is static, which means that if you 
> try to create another client for tests, the login object will be the first 
> one you've set for all runs. I've experienced this with 3.4.6.
> # There are a number of properties spread across the code that do not appear 
> in the docs. For example, zookeeper.allowSaslFailedClients isn't documented 
> afaict.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ZOOKEEPER-2314) Improvements to SASL

2016-03-21 Thread Flavio Junqueira (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flavio Junqueira updated ZOOKEEPER-2314:

Summary: Improvements to SASL  (was: Improve SASL documentation)

> Improvements to SASL
> 
>
> Key: ZOOKEEPER-2314
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2314
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.4.6, 3.5.1
>Reporter: Flavio Junqueira
>Assignee: Flavio Junqueira
>Priority: Blocker
> Fix For: 3.4.9, 3.5.2, 3.6.0
>
>
> Points that occur to me right now:
> # The login object in ZooKeeperSaslClient is static, which means that if you 
> try to create another client for tests, the login object will be the first 
> one you've set for all runs. I've experienced this with 3.4.6.
> # There are a number of properties spread across the code that do not appear 
> in the docs. For example, zookeeper.allowSaslFailedClients isn't documented 
> afaict.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)