[
https://issues.apache.org/jira/browse/HBASE-8662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687156#comment-13687156
]
Jimmy Xiang commented on HBASE-8662:
------------------------------------
[~toffer], very simple solution. That's good. The difference mainly is that you
switch the user based on the current user using doAs, and don't save a context
per user. However, the HConnection(and the ticket) is cached in the HBaseAdmin
and HTablePool. I was wondering how the RPC client gets the current ugi (the
ticket) with your patch.
> [rest] support impersonation
> ----------------------------
>
> Key: HBASE-8662
> URL: https://issues.apache.org/jira/browse/HBASE-8662
> Project: HBase
> Issue Type: Sub-task
> Components: REST, security
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.98.0
>
> Attachments: secure_rest.patch, trunk-8662.patch, trunk-8662_v2.patch
>
>
> Currently, our client API uses a fixed user: the current user. It should
> accept a user passed in, if authenticated.
--
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
