[HBASE-16141] Unwind use of UserGroupInformation.doAs() to convey requester identity in coprocessor upcalls

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Later
• Component/s: Coprocessors, security
• Assignee: Unassigned
• Reporter: Gary Helmling
• Created: 29/Jun/16 05:24
• Updated: 06/Mar/20 23:54
• Resolved: 06/Mar/20 23:54

Description

In discussion on HBASE-16115, there is some discussion of whether UserGroupInformation.doAs() is the right mechanism for propagating the original requester's identify in certain system contexts (splits, compactions, some procedure calls). It has the unfortunately of overriding the current user, which makes for very confusing semantics for coprocessor implementors. We should instead find an alternate mechanism for conveying the caller identity, which does not override the current user context.

I think we should instead look at passing this through as part of the ObserverContext passed to every coprocessor hook.

Issue Links

• relates to: HBASE-16115 Missing security context in RegionObserver coprocessor when a compaction/split is triggered manually
• relates to: PHOENIX-3037 Setup proper security context in compaction/split coprocessor hooks

Sub-Tasks

• Identify calling user in ObserverContext: Resolved
• Eliminate use of UGI.doAs() in AccessController testing: Open
• Backport HBASE-16217 to branch-1: Resolved