Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
3.4.6
-
None
-
None
Description
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
Attachments
Attachments
Issue Links
- is related to
-
ZOOKEEPER-2344 Provide more diagnostics/stack traces on SASL Auth failure
- Open