[ https://issues.apache.org/jira/browse/HBASE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532954#comment-13532954 ]
Hudson commented on HBASE-7357: ------------------------------- Integrated in HBase-TRUNK #3627 (See [https://builds.apache.org/job/HBase-TRUNK/3627/]) HBASE-7357 Use hbase.security.authentication for HBaseClient / HBaseServer negotiation (Revision 1422185) Result = FAILURE garyh : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/ProtobufRpcEngine.java * /hbase/trunk/hbase-server/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 > Attachments: 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