[ 
https://issues.apache.org/jira/browse/HIVE-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745552#comment-13745552
 ] 

Hive QA commented on HIVE-4601:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12598990/HIVE-4601.4.patch

{color:green}SUCCESS:{color} +1 2893 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/490/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/490/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.
                
> WebHCat, Templeton need to support proxy users
> ----------------------------------------------
>
>                 Key: HIVE-4601
>                 URL: https://issues.apache.org/jira/browse/HIVE-4601
>             Project: Hive
>          Issue Type: Improvement
>          Components: HCatalog
>    Affects Versions: 0.11.0
>            Reporter: Dilli Arumugam
>            Assignee: Eugene Koifman
>              Labels: proxy, templeton
>             Fix For: 0.12.0
>
>         Attachments: HIVE-4601.2.patch, HIVE-4601.3.patch, HIVE-4601.4.patch, 
> HIVE-4601.patch
>
>
> We have a use case where a Gateway would provide unified and controlled 
> access to secure hadoop cluster.
> The Gateway itself would authenticate to secure WebHDFS, Oozie and Templeton 
> with SPNego.
> The Gateway would authenticate the end user with http basic and would assert 
> the end user identity as douser argument in the calls to downstream WebHDFS, 
> Oozie and Templeton.
> This works fine with WebHDFS and Oozie. But, does not work for Templeton as 
> Templeton does not support proxy users.
> Hence, request to add this improvement to Templeton.

--
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

Reply via email to