You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2017/03/20 17:57:42 UTC
[jira] [Resolved] (HBASE-12579) Move obtainAuthTokenForJob()
methods out of User
[ https://issues.apache.org/jira/browse/HBASE-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling resolved HBASE-12579.
-----------------------------------
Resolution: Duplicate
The methods were deprecated and the existing usage was removed as part of HBASE-12493. I guess I left this open for the final removal of the deprecated methods from the next major release. The removal was done as part of HBASE-14208.
> Move obtainAuthTokenForJob() methods out of User
> ------------------------------------------------
>
> Key: HBASE-12579
> URL: https://issues.apache.org/jira/browse/HBASE-12579
> Project: HBase
> Issue Type: Improvement
> Components: security
> Reporter: Gary Helmling
>
> The {{User}} class currently contains some utility methods to obtain HBase authentication tokens for the given user. However, these methods initiate an RPC to the {{TokenProvider}} coprocessor endpoint, an action which should not be part of the User class' responsibilities.
> This leads to a couple of problems:
> # The way the methods are currently structured, it is impossible to integrate them with normal connection management for the cluster (the TokenUtil class constructs its own HTable instance internally).
> # The User class is logically part of the hbase-common module, but uses the TokenUtil class (part of hbase-server, though it should probably be moved to hbase-client) through reflection, leading to a hidden dependency.
> The {{obtainAuthTokenForJob()}} methods should be deprecated and the process of obtaining authentication tokens should be moved to use the normal connection lifecycle.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)