[
https://issues.apache.org/jira/browse/HBASE-12831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296415#comment-14296415
]
Hudson commented on HBASE-12831:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #121 (See
[https://builds.apache.org/job/HBase-1.1/121/])
HBASE-12831 Changing the set of vis labels a user has access to doesn't
generate an audit log event (busbey: rev
a2d8b0e52bc412ed857a0b16abef34a243ffefd0)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityController.java
* conf/log4j.properties
> Changing the set of vis labels a user has access to doesn't generate an audit
> log event
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-12831
> URL: https://issues.apache.org/jira/browse/HBASE-12831
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.0, 2.0.0, 0.98.6
> Reporter: Sean Busbey
> Assignee: Ashish Singhi
> Labels: audit
> Fix For: 1.0.1, 0.98.11
>
> Attachments: HBASE-12831-v2.patch, HBASE-12831-v3.patch,
> HBASE-12831-v5.patch, HBASE-12831-v6.patch, HBASE-12831.patch,
> HBASE-12831v4.patch
>
>
> Right now, the AccessController makes sure that (when users care about audit
> events) we generate an audit log event for any access change, like granting
> or removing a permission from a user.
> When the set of labels a user has access to is altered, it gets handled by
> the VisibilityLabelService and we don't log anything to the audit log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
