You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/06/09 06:02:02 UTC
[jira] [Commented] (HBASE-7357) HBaseClient and HBaseServer should
use hbase.security.authentication when negotiating authentication
[ https://issues.apache.org/jira/browse/HBASE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021554#comment-14021554 ]
Hudson commented on HBASE-7357:
-------------------------------
FAILURE: Integrated in HBase-TRUNK #5187 (See [https://builds.apache.org/job/HBase-TRUNK/5187/])
HBASE-7394 Document security config requirements from HBASE-7357 (Misty Stanley-Jones) (stack: rev 8c43acfd45967f39f8a2bfc4be2814f9eef0992c)
* src/main/docbkx/security.xml
> 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
> Fix For: 0.94.4, 0.95.0
>
> Attachments: HBASE-7357.patch, HBASE-7357_0.94.patch, HBASE-7357_0.94_2.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 was sent by Atlassian JIRA
(v6.2#6252)