[
https://issues.apache.org/jira/browse/HBASE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537926#comment-13537926
]
Hudson commented on HBASE-7357:
-------------------------------
Integrated in HBase-0.94-security #87 (See
[https://builds.apache.org/job/HBase-0.94-security/87/])
HBASE-7357 Use hbase.security.authentication for client / server security
negotiation (Revision 1423997)
Result = SUCCESS
garyh :
Files :
*
/hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureClient.java
*
/hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/security/User.java
> 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.96.0, 0.94.4
>
> 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
