[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740370#comment-13740370
]
Jesse Yates commented on HBASE-9221:
------------------------------------
This came up at Salesforce where we have to connect to a secure and insecure
cluster from the same JVM. To enable this, we needed to rewrite
UserGroupInformation to correctly support this case. However, this meant we
needed to change how we obtain a o.a.h.h.security.User (to bind it to the right
Configuration).
> 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
>
> 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
