[
https://issues.apache.org/jira/browse/HBASE-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931983#comment-15931983
]
stack commented on HBASE-12579:
-------------------------------
Yeah, I could not find obtainAuthTokenForJob in the code base either. My guess
though is it just got renamed and the root problem may still exist. Our
[~ghelmling] knows this stuff well... maybe when he has a moment he can make a
ruling here.
> 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)
