[
https://issues.apache.org/jira/browse/HBASE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741654#comment-13741654
]
Hudson commented on HBASE-9227:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK #4398 (See
[https://builds.apache.org/job/HBase-TRUNK/4398/])
HBASE-9227 RESTServer should handle the loginUser correctly (stack: rev 1514440)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java
> 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, 9227-4.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
