[ 
https://issues.apache.org/jira/browse/HIVE-21892?focusedWorklogId=263369&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-263369
 ]

ASF GitHub Bot logged work on HIVE-21892:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Jun/19 22:28
            Start Date: 19/Jun/19 22:28
    Worklog Time Spent: 10m 
      Work Description: prasanthj commented on issue #678: HIVE-21892: Trusted 
domain authentication should look at X-Forwarded-For header as well
URL: https://github.com/apache/hive/pull/678#issuecomment-503770022
 
 
   Patch merged to master. Closing PR. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 263369)
    Time Spent: 1h 10m  (was: 1h)

> Trusted domain authentication should look at X-Forwarded-For header as well
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-21892
>                 URL: https://issues.apache.org/jira/browse/HIVE-21892
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 4.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>         Attachments: HIVE-21892.1.patch, HIVE-21892.2.patch
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> HIVE-21783 added trusted domain authentication. However, it looks only at 
> request.getRemoteAddr() which works in most cases where there are no 
> intermediate forward/reverse proxies. In trusted domain scenarios, if there 
> intermediate proxies, the proxies typically append its own ip address 
> "X-Forwarded-For" header. The X-Forwarded-For will look like clientIp -> 
> proxyIp1 -> proxyIp2. The left most ip address in the X-Forwarded-For 
> represents the real client ip address. For such scenarios, add a config to 
> optionally look at X-Forwarded-For header when available to determine the 
> real client ip. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to