[
https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741091#comment-13741091
]
Jimmy Xiang edited comment on HBASE-9227 at 8/15/13 4:03 PM:
-------------------------------------------------------------
[~devaraj], User.getCurrent().getUGI() login again? I think that's why I used
login and return UGI. My understanding is that the issue is not setting the
user after login in, instead of the way to log in, right?
was (Author: jxiang):
+1
> 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
