[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HBASE-9221:
-------------------------------
Attachment: hbase-9221-0.94-v1.patch
Attaching updated patch for 0.94 - fixes small test failure in
TestMasterServlet that UserProvider#instantiate expects a non-null
configuration. It will always be non-null, from the MasterServlet except in the
test case where the mock HBaseAdmin was not setup to pass along the
configuration.
Hoping to commit this soon to make the 0.94.12 deadline...
> Provide interface for getting a User in the client
> --------------------------------------------------
>
> Key: HBASE-9221
> URL: https://issues.apache.org/jira/browse/HBASE-9221
> Project: HBase
> Issue Type: Improvement
> Components: Client, hadoop2, security
> Affects Versions: 0.98.0, 0.95.2, 0.94.12
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch
>
>
> Sometimes, users will want to provide their own User class depending on the
> type of security they will support in their local environment. For instance,
> running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
> the UserGroupInformation.
> This issue abstracts out the mechanism by which we obtain an
> o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
> extented as a Hadoop 1/2 shim as well as supporting custom authentication
> code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
