You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Meyer Kizner (JIRA)" <ji...@apache.org> on 2016/11/28 18:37:58 UTC

[jira] [Updated] (ZOOKEEPER-2346) SASL Auth failure manifested to client as connection refusal

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

Meyer Kizner updated ZOOKEEPER-2346:
------------------------------------
    Attachment: ZOOKEEPER-2346.patch

> 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)