[
https://issues.apache.org/jira/browse/HBASE-9706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788411#comment-13788411
]
Hadoop QA commented on HBASE-9706:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12607203/JIRA-9706-1-0.95-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7482//console
This message is automatically generated.
> Improve detection of secure ZooKeeper
> -------------------------------------
>
> Key: HBASE-9706
> URL: https://issues.apache.org/jira/browse/HBASE-9706
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.94.4, 0.95.0
> Environment: Java 6, RHEL, HBase 0.94.9
> Reporter: Eric Yang
> Assignee: Eric Yang
> Fix For: 0.98.0, 0.96.1
>
> Attachments: JIRA-9706-0.94.patch, JIRA-9706-0.95-trunk.patch,
> JIRA-9706-1-0.94.patch, JIRA-9706-1-0.95-trunk.patch
>
>
> HBase client code assumes ZooKeeper is secured, as long as there is a
> java.security.auth.login.config property being set. When HBase client is
> embedded in other java program with other security configuration, it can
> produce wrong assumption that ZooKeeper is secured. Ideally,
> isSecureZooKeeper method should detect Jaas configuration specifically for
> ZooKeeper to ensure that client program doesn't have a false positive
> detection.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
