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 2017/03/13 16:22:05 UTC

[jira] [Updated] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure

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

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

> Provide more diagnostics/stack traces on SASL Auth failure
> ----------------------------------------------------------
>
>                 Key: ZOOKEEPER-2344
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2344
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: java client, server
>    Affects Versions: 3.4.7, 3.5.1
>            Reporter: Steve Loughran
>             Fix For: 3.5.4, 3.6.0
>
>
> When Kerberos decides it doesn't want to work, the JRE libraries provide some terse and unhelpful error messages.
> The only way to debug the problem is (a) to have complete stack traces and (b) as much related information as possible.
> Zookeeper could do more here. Currently too much of the code loses stack traces; sometimes auth errors aren't reported back to the client (the connection is closed) +others
> Everyone who has tried to diagnose kerberos problems will appreciate improvements here



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