[
https://issues.apache.org/jira/browse/RANGER-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18083351#comment-18083351
]
Abhishek Kumar commented on RANGER-5499:
----------------------------------------
Follow-up commits:
master:
[https://github.com/apache/ranger/commit/1b74f00d9b6357e0ee4c7c64de73aa938f2c0a0b]
ranger-2.9:
https://github.com/apache/ranger/commit/7de6ea8d9e6fb3d950961afbd2ee38e257819b6b
> Support header based authentication
> -----------------------------------
>
> Key: RANGER-5499
> URL: https://issues.apache.org/jira/browse/RANGER-5499
> Project: Ranger
> Issue Type: New Feature
> Components: admin, kms
> Reporter: Madhan Neethiraj
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0, 2.8.1, 2.9.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Ranger servers currently support multiple authentication mechanisms,
> including Kerberos, username/password (LDAP, local users), JWT, SSO. To
> support deployments behind proxy servers that handle authentication, Ranger
> servers should support header based authentication. When this authentication
> is enabled, Ranger should look for a configured HTTP header to find the user
> name. In addition to username, groups the user belongs to also can be
> provided by a HTTP header. I suggest following configurations:
> * ranger.authn.http-header.enabled
> * ranger-authn.http-header.username
> * ranger-authn.http-header.usergroups
> * ranger-authn.http-header.requestid
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
