You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sushanth Sowmyan (JIRA)" <ji...@apache.org> on 2016/06/01 21:34:59 UTC

[jira] [Commented] (HIVE-13418) HiveServer2 HTTP mode should support X-Forwarded-Host header for authorization/audits

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

Sushanth Sowmyan commented on HIVE-13418:
-----------------------------------------

Marking fix version per Lefty's comment above.

> HiveServer2 HTTP mode should support X-Forwarded-Host header for authorization/audits
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-13418
>                 URL: https://issues.apache.org/jira/browse/HIVE-13418
>             Project: Hive
>          Issue Type: New Feature
>          Components: Authorization, HiveServer2
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 2.1.0
>
>         Attachments: HIVE-13418.1.patch
>
>
> Apache Knox acts as a proxy for requests coming from the end users. In these cases, the IP address that HiveServer2 passes to the authorization/audit plugins via the HiveAuthzContext object only the IP address of the proxy, and not the end user.
> For auditing purposes, the IP address of the end user and any proxies in between are useful.
> HiveServer2 should pass the information from  'X-Forwarded-Host' header to the HiveAuthorizer plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)