[
https://issues.apache.org/jira/browse/RANGER-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-5499.
------------------------------------
Fix Version/s: 3.0.0
2.8.1
2.9.0
Resolution: Fixed
Merged in master:
[https://github.com/apache/ranger/commit/2345c1d79d63f632bab237a8b08426d056b30f6c]
[https://github.com/apache/ranger/commit/a6c21a19aa2522f882301bccce03e6c28701522a]
Merged in ranger-2.8:
[https://github.com/apache/ranger/commit/d40fac0b695007394dab90be0b8384f2c51aea03]
[https://github.com/apache/ranger/commit/9a57bab6237a947d9864f699de2c31b00fc280bc]
Merged in ranger-2.9:
[https://github.com/apache/ranger/commit/1e12062734992e5de38a8b910e0183c31af2d2c9]
https://github.com/apache/ranger/commit/daf23a439bae1f3e300ec2743347099f522e2d00
> 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: 2h
> 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)
