[ https://issues.apache.org/jira/browse/HBASE-12745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258017#comment-14258017 ]
Jerry He commented on HBASE-12745: ---------------------------------- Hi, [~anoop.hbase] bq. 4) But client side get_auths call will only get the result explicit for that user only or for that group (if parameter is @group) only. I was thinking that if we were to show all auth labels (explicit or via group), how would we give a consistent behavior expectation with clear_auths, since the implied group labels can not be cleared with clear_auths for that user. Any suggestions or preference? > Visibility Labels: support visibility labels for user groups. > -------------------------------------------------------------- > > Key: HBASE-12745 > URL: https://issues.apache.org/jira/browse/HBASE-12745 > Project: HBase > Issue Type: Improvement > Components: security > Affects Versions: 1.0.0, 0.98.9, 0.99.2 > Reporter: Jerry He > Assignee: Jerry He > Fix For: 2.0.0 > > Attachments: HBASE-12745-master-v1.patch > > > The thinking is that we should support visibility labels to be associated > with user groups. > We will then be able grant visibility labels to a group in addition to > individual users, which provides convenience and usability. > We will use '@group' to denote a group name, as similarly done in > AcccessController. > For example, > {code} > set_auths '@group1', ['SECRET','PRIVATE'] > {code} > {code} > get_auth '@group1' > {code} > A user belonging to 'group1' will have all the visibility labels granted to > 'group1' > We'll also support super user groups as specified in hbase-site.xml. > The code update will mainly be on the server side VisibilityLabelService > implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)