[
https://issues.apache.org/jira/browse/HBASE-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659557#comment-14659557
]
Francis Liu commented on HBASE-14169:
-------------------------------------
Sounds good. I've updated the patch to check for system user. Also....
[~apurtell] and [~mbertozzi], Should I follow the same semantics to as acl
table to propagate requests (ie use zk as a message bus), seemed a bit clunky
and overly complicated to me for this particular case? I've uploaded a draft
which sends the rpc request to the master and the master propagates it to the
RSes, since the master has the list of online servers on-hand. I haven't read
how ProcedureV2 plans to propagate messages. So let me know what would work
best.
> API to refreshSuperUserGroupsConfiguration
> ------------------------------------------
>
> Key: HBASE-14169
> URL: https://issues.apache.org/jira/browse/HBASE-14169
> Project: HBase
> Issue Type: New Feature
> Reporter: Francis Liu
> Assignee: Francis Liu
> Attachments: HBASE-14169.patch, HBASE-14169_2.patch
>
>
> For deployments that use security. User impersonation (AKA doAs()) is needed
> for some services (ie Stargate, thriftserver, Oozie, etc). Impersonation
> definitions are defined in a xml config file and read and cached by the
> ProxyUsers class. Calling this api will refresh cached information,
> eliminating the need to restart the master/regionserver whenever the
> configuration is changed.
> Implementation just adds another method to AccessControlService.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
