hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Szehon Ho (JIRA)" <>
Subject [jira] [Updated] (HIVE-6182) LDAP Authentication errors need to be more informative
Date Sat, 11 Jan 2014 02:57:50 GMT


Szehon Ho updated HIVE-6182:

    Attachment: HIVE-6182.patch

Submitting a fix.

The log now shows more information:

2014-01-10 18:53:09,609 ERROR transport.TSaslTransport ( - SASL
negotiation failure Error validating the login [Caused by
Error validating LDAP user [Caused by javax.naming.InvalidNameException: [LDAP: error code
34 - invalid DN]]]
	at org.apache.hive.service.auth.PlainSaslServer.evaluateResponse(
	at org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrResponse(

> LDAP Authentication errors need to be more informative
> ------------------------------------------------------
>                 Key: HIVE-6182
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Authentication
>    Affects Versions: 0.13.0
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>         Attachments: HIVE-6182.patch
> There are a host of errors that can happen when logging into an LDAP-enabled Hive-server2
from beeline.  But for any error there is only a generic log message:
> {code}
> SASL negotiation failure
> PLAIN auth failed: Error validating LDAP user
> 	at
> 	at org.apache.thrift.transport.TSaslTransport$SaslParticipant.evaluateChallengeOrRespons
> {code}
> And on Beeline side there is only an even more unhelpful message:
> {code}
> Error: Invalid URL: jdbc:hive2://localhost:10000/default (state=08S01,code=0)
> {code}
> It would be good to print out the underlying error message at least in the log, if not
beeline.   But today they are swallowed.  This is bad because the underlying message is the
most important, having the error codes as shown here : [LDAP error code|]
> The beeline seems to throw that exception for any error during connection, authetication
or otherwise.

This message was sent by Atlassian JIRA

View raw message