[
https://issues.apache.org/jira/browse/HIVE-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930796#comment-13930796
]
Hive QA commented on HIVE-6558:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12633729/HIVE-6558.2.patch
{color:green}SUCCESS:{color} +1 5380 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1702/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1702/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12633729
> HiveServer2 Plain SASL authentication broken after hadoop 2.3 upgrade
> ---------------------------------------------------------------------
>
> Key: HIVE-6558
> URL: https://issues.apache.org/jira/browse/HIVE-6558
> Project: Hive
> Issue Type: Bug
> Components: Authentication, HiveServer2
> Affects Versions: 0.13.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Priority: Blocker
> Attachments: HIVE-6558.2.patch, HIVE-6558.2.patch
>
>
> Java only includes Plain SASL client and not server. Hence HiveServer2
> includes a Plain SASL server implementation. Now Hadoop has its own Plain
> SASL server [HADOOP-9020|https://issues.apache.org/jira/browse/HADOOP-9020]
> which is part of Hadoop 2.3
> [release|http://hadoop.apache.org/docs/r2.3.0/hadoop-project-dist/hadoop-common/releasenotes.html].
> The two servers use different Sasl callbacks and the servers are registered
> in java.security.Provider via static code. As a result the HiveServer2
> instance could be using Hadoop's Plain SASL server which breaks the
> authentication.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
