hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-12885) LDAP Authenticator improvements
Date Tue, 19 Jan 2016 03:37:40 GMT


Hive QA commented on HIVE-12885:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 6 failed/errored test(s), 10024 tests executed
*Failed tests:*
TestHWISessionManager - did not produce a TEST-*.xml file

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 6 tests failed

This message is automatically generated.

ATTACHMENT ID: 12782920 - PreCommit-HIVE-TRUNK-Build

> LDAP Authenticator improvements
> -------------------------------
>                 Key: HIVE-12885
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 1.1.0
>            Reporter: Naveen Gangam
>            Assignee: Naveen Gangam
>         Attachments: HIVE-12885.patch
> Currently Hive's LDAP Atn provider assumes certain defaults to keep its configuration
> 1) One of the assumptions is the presence of an attribute "distinguishedName". In certain
non-standard LDAP implementations, this attribute may not be available. So instead of basing
all ldap searches on this attribute, getNameInNamespace() returns the same value. So this
API is to be used instead.
> 2) It also assumes that the "user" value being passed in, will be able to bind to LDAP.
However, certain LDAP implementations, by default, only allow the full DN to be used, just
short user names are not permitted. We will need to be able to support short names too when
hive configuration only has "BaseDN" specified (not userDNPatterns). So instead of hard-coding
"uid" or "CN" as keys for the short usernames, it probably better to make this a configurable

This message was sent by Atlassian JIRA

View raw message