[
https://issues.apache.org/jira/browse/HBASE-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396776#comment-16396776
]
Appy commented on HBASE-19093:
------------------------------
The title says "Check Admin/Table to ensure all operations go via
AccessControl" and [~balazs.meszaros] already did the work of figuring that out
and filed relevant jiras under HBASE-18799 (parent of this one too). So i think
we should at least close this one and mark fixVersion of HBASE-18799 as 2.0.0.
But that's just passing the baton, and not finishing the race.
Status of HBASE-18799 is, it has 2 remaining jiras- HBASE-19402, HBASE-19403.
Code wise, it's probably just an hour of work. But more than that, am unsure of
some aspects in those jiras. There's pending discussion on them.
> Check Admin/Table to ensure all operations go via AccessControl
> ---------------------------------------------------------------
>
> Key: HBASE-19093
> URL: https://issues.apache.org/jira/browse/HBASE-19093
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: Balazs Meszaros
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-19093.master.001.patch,
> HBASE-19093.master.002.patch, RegionObserver.txt
>
>
> A cursory review of Admin Interface has a bunch of methods as open, with out
> AccessControl checks. For example, procedure executor has not check on it.
> This issue is about given the Admin and Table Interfaces a once-over to see
> what is missing and to fill in access control where missing.
> This is a follow-on from work over in HBASE-19048
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
