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 2016/07/12 23:29:20 UTC

[jira] [Commented] (HBASE-16217) Identify calling user in ObserverContext

    [ https://issues.apache.org/jira/browse/HBASE-16217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373943#comment-15373943 ] 

Gary Helmling commented on HBASE-16217:
---------------------------------------

Also posted patch on review board: https://reviews.apache.org/r/49970/

> Identify calling user in ObserverContext
> ----------------------------------------
>
>                 Key: HBASE-16217
>                 URL: https://issues.apache.org/jira/browse/HBASE-16217
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors, security
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16217.master.001.patch
>
>
> We already either explicitly pass down the relevant User instance initiating an action through the call path, or it is available through RpcServer.getRequestUser().  We should carry this through in the ObserverContext for coprocessor upcalls and make use of it for permissions checking.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)