[
https://issues.apache.org/jira/browse/ZOOKEEPER-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702787#comment-15702787
]
Michael Han commented on ZOOKEEPER-2346:
----------------------------------------
[~mkizner] Patch looks good - the missing part is tests (for both Java and C
client). Also FYI I am using similar approach in ZOOKEEPER-1634 (work in
progress), so we might want to consolidate our patches at some point if you are
adding more tests. Though my change in ZOOKEEPER-1634 will be a superset of
your change (including all tests) here so you could also wait and review
ZOOKEEPER-1634 when it's ready.
> SASL Auth failure manifested to client as connection refusal
> ------------------------------------------------------------
>
> Key: ZOOKEEPER-2346
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2346
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.6
> Reporter: Steve Loughran
> Assignee: Meyer Kizner
> Attachments: ZOOKEEPER-2346.patch, ZOOKEEPER-2346.patch
>
>
> If a client can't authenticate via sasl then (a) the stack trace is lost on
> the server logs, and (b) it is exposed to the client as a connection refusal.
> This results in curator retrying many times before giving up —and with the
> cause being misinterpreted as a server-down problem, rather than a
> client-not-trusted problem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
