[HBASE-7357] HBaseClient and HBaseServer should use hbase.security.authentication when negotiating authentication

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.94.4, 0.95.0
• Component/s: security
• Hadoop Flags: Incompatible change, Reviewed

Release Note

This is a slightly incompatible change.
HBase SASL connection negotiation is now enabled by setting hbase.security.authentication rather than hadoop.security.authentication.

• Assignee: Gary Helmling
• Reporter: Gary Helmling
• Created: 14/Dec/12 21:25
• Updated: 09/Jun/14 04:01
• Resolved: 19/Dec/12 18:42

Description

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().

Issue Links

• is depended upon by: HBASE-6788 Convert AuthenticationProtocol to protocol buffer service
• is related to: HBASE-7394 Document security config requirements from HBASE-7357