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

Posted to dev@zookeeper.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/12/15 18:59:47 UTC

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

Steve Loughran created ZOOKEEPER-2346:
-----------------------------------------

             Summary: 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


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)