Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Later
-
None
-
None
-
None
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.
Attachments
Issue Links
- relates to
-
HBASE-16115 Missing security context in RegionObserver coprocessor when a compaction/split is triggered manually
- Resolved
-
PHOENIX-3037 Setup proper security context in compaction/split coprocessor hooks
- Closed