[ZOOKEEPER-2035] diagnostics on SASL connection problems doesn't match error strings sent back

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.4.6

Environment

Java 1.7.0.67 on OS/X

• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 13/Sep/14 17:33
• Updated: 15/Dec/15 17:47

Description

The diagnostics code in ZooKeeperSaslClient.createSaslToken() which looks for a "("Mechanism level: Server not found in Kerberos database (7) - UNKNOWN_SERVER)" error string isn't finding a match ... the text now appears to be (Mechanism level: Server not found in Kerberos database (7) - Server not found in Kerberos database)

Issue Links

• is related to: ZOOKEEPER-2344 Provide more diagnostics/stack traces on SASL Auth failure