[
https://issues.apache.org/jira/browse/RANGER-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-4079:
-------------------------------------
Attachment: RANGER-4079.patch
> Python client to use the given Ranger endpoint, instead of its baseURL
> ----------------------------------------------------------------------
>
> Key: RANGER-4079
> URL: https://issues.apache.org/jira/browse/RANGER-4079
> Project: Ranger
> Issue Type: Bug
> Components: intg
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: RANGER-4079.patch
>
>
> Ranger can be deployed behind a proxy which can result in Ranger endpoint to
> include a subpath, like [https://hostname:6182/ranger] (instead of
> [https://hostname:6182|https://hostname:6182)./]).
> Python client for Ranger strips the last path of the such URL while
> constructing the URL for REST APIs - like
> {{{}https://hostname:6182/service/public/v2/api/policy{}}}. This results in
> REST API calls to fail since the URL doesn't include {{{}/ranger{}}}. Ranger
> Python client needs to be updated to address this issue.
> In addition, it will be desirable to be able to send few headers and query
> parameters in each API call, for example to send requestId header or tenantId
> as a parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)