[HBASE-7663] [Per-KV security] Visibility labels

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.98.0
• Fix Version/s: 0.98.0
• Component/s: Coprocessors, security
• Hadoop Flags: Reviewed

Release Note

VisibilityController CP handles the visibility
The visibility labels are stored as tags with KVs
Use Mutation#setCellVisibility(new CellVisibility(<labelExp>)); to add visibility expressions to cells
The label expression can contain visibility labels joined with logical expressions &, | and !. Also using (, ) one can specify the precedence order
Eg : SECRET & CONFIDENTIAL & !PUBLIC
Please note that passing CellVisibility in a Delete mutation is illegal.

During read, (Scan/Get) one can specify labels associated with that, in Authorizations
scan.setAuthorizations(new Authorizations(SECRET, CONFIDENTIAL));


Visibility Label admin operations
----------------------------------------
Labels can be added to the system using VisibilityClient#addLabels(). Also can use add_labels shell command
Only super user (hbase.superuse) have permission to add the labels into the system.
A set of labels can be associated for a user using setAuths. VisibilityClient#setAuths()
Similarly labels can be removed from user auths using clearAuths.
getAuths API can be used to view user auths.
Also there is support for set_auths, clear_auths and get_auths shell commands
Same way as in addLabels, only super user have permission for these operations.
When AccessController is ON the permission checks are handled by AC.
Using AC along with Visibility is optional. When AC is not available, permission checks are done at VisibilityController level itself.

• Assignee: Anoop Sam John
• Reporter: Andrew Purtell
• Created: 24/Jan/13 22:32
• Updated: 20/Nov/15 11:55
• Resolved: 19/Nov/13 05:45

Description

Implement Accumulo-style visibility labels. Consider the following design principles:

• Coprocessor based implementation
• Minimal to no changes to core code
• Use KeyValue tags (HBASE-7448) to carry labels
• Use OperationWithAttributes# {get,set}

  Attribute for handling visibility labels in the API

• Implement a new filter for evaluating visibility labels as KVs are streamed through.

This approach would be consistent in deployment and API details with other per-KV security work, supporting environments where they might be both be employed, even stacked on some tables.

See the parent issue for more discussion.

Issue Links

• depends upon: HBASE-9962 Improve tag iteration
• is depended upon by: HBASE-9884 Add Thrift and REST support for Visibility Labels
• is related to: HBASE-7254 Refactor AccessController ZK-mediated permissions cache into a generic mechanism
• relates to: HBASE-12346 Scan's default auths behavior under Visibility labels
• relates to: HBASE-9832 Add MR support for Visibility labels
• relates to: HBASE-12373 Provide a command to list visibility labels
• relates to: HBASE-12466 Document visibility scan label generator usage and behavior