[
https://issues.apache.org/jira/browse/HBASE-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536241#comment-13536241
]
Gary Helmling commented on HBASE-7357:
--------------------------------------
Committed to 0.94 branch.
bq. Does this need a documentation change somewhere aswell? Can do as separate
jira if needed.
Yes, I checked the ref guide and it looks like we should update the security
docs to show hadoop.security.authentication in the configuration in addition to
hbase.security.authentication. I'll open another ticket for the doc update.
> 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
