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

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2016/10/28 23:53:58 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15616964#comment-15616964 ] 

Michael Han edited comment on ZOOKEEPER-2346 at 10/28/16 11:53 PM:
-------------------------------------------------------------------

[~fpj] should be able to assign the issue to you [~mkizner].
Alternatively, you can send a pull request to [apache/zookeeper|https://github.com/apache/zookeeper].


was (Author: hanm):
[~fpj] should be able to assign the issue to you [~mkizner].
Alternatively, you can send a pull request, please refer to [this link|https://cwiki.apache.org/confluence/display/ZOOKEEPER/Merging+Github+Pull+Requests] on how to.

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