[
https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741181#comment-13741181
]
Devaraj Das commented on HBASE-9227:
------------------------------------
[~jxiang], User.login would do the login and save the state in loginUser. Later
when User.getCurrent() is called, it would get that UGI (since getCurrentUser
in Hadoop's UGI class returns the loginUser UGI unless called within a doAs for
a different user). I'll also try to test the patch for the regular user
(non-impersonation case).
> RESTServer should handle the loginUser correctly
> ------------------------------------------------
>
> Key: HBASE-9227
> URL: https://issues.apache.org/jira/browse/HBASE-9227
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.95.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.95.2
>
> Attachments: 9227-1.txt, 9227-2.txt, 9227-3.txt
>
>
> HBASE-8662 introduced a change by which the realUser in the method
> RESTServer.main() gets assigned to the loginUser only when the config
> hbase.rest.authentication.type is set to something (like "kerberos").
> I think we should set the realUser to loginUser even when the config
> hbase.rest.authentication.type is null. Without that the regular
> (non-impersonated) accesses also fail.
--
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
