hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16217) Identify calling user in ObserverContext
Date Fri, 22 Jul 2016 00:19:20 GMT

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

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

Committed to master.  Working on a patch against branch-1 to account for differences there.

> 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, HBASE-16217.master.002.patch, HBASE-16217.master.003.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)

Mime
View raw message