You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2012/12/14 23:16:14 UTC

[jira] [Updated] (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:all-tabpanel ]

Gary Helmling updated HBASE-7357:
---------------------------------

    Status: Patch Available  (was: Open)
    
> 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.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