[
https://issues.apache.org/jira/browse/HBASE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Helmling resolved HBASE-4372.
----------------------------------
Resolution: Invalid
I think you misunderstand the purpose of User.IS_SECURE_HADOOP. It is there to
differentiate between API incompatible versions of UserGroupInformation from
vanilla 0.20 to secure 0.20+ using reflection.
Whether or not kerberos authentication is enabled makes no difference in
determining whether we need to call UserGroupInformation.getCurrentUGI() vs.
UserGroupInformation.getCurrentUser(), for example.
If you simply want access to whether or not secure authentication is enabled,
there is a patch against HBASE-4180 that adds a User.isSecurityEnabled() method.
> IS_SECURE_HADOOP should be set to true only if security is turned on.
> ---------------------------------------------------------------------
>
> Key: HBASE-4372
> URL: https://issues.apache.org/jira/browse/HBASE-4372
> Project: HBase
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Attachments: HBASE-4372.1.patch
>
>
> Currently, IS_SECURE_HADOOP is set to true if UserGroupInformation has a
> method isSecurityEnabled. It should be set to true only if security is turned
> on as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
