hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7357) HBaseClient and HBaseServer should use hbase.security.authentication when negotiating authentication
Date Tue, 18 Dec 2012 19:44:14 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535212#comment-13535212
] 

Hadoop QA commented on HBASE-7357:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12561547/HBASE-7357_0.94_2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3591//console

This message is automatically generated.
                
> HBaseClient and HBaseServer should use hbase.security.authentication when negotiating
authentication
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7357
>                 URL: https://issues.apache.org/jira/browse/HBASE-7357
>             Project: HBase
>          Issue Type: Bug
>          Components: security
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>         Attachments: HBASE-7357_0.94_2.patch, HBASE-7357_0.94.patch, HBASE-7357.patch
>
>
> This came up in the context of testing HBASE-6788.  Currently HBaseClient and HBaseServer
call UserGroupInformation.isSecurityEnabled() when determining whether or not to use SASL
to negotiate connections.  This means they are using the hadoop.security.authentication configuration
value.  Since this is in the context of HBase RPC connections, it seems more correct to use
the hbase.security.authentication configuration value by calling User.isHBaseSecurityEnabled().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message