You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Abhishek Kumar (Jira)" <ji...@apache.org> on 2026/05/25 21:22:00 UTC

[jira] [Updated] (RANGER-5499) Support header based authentication

     [ https://issues.apache.org/jira/browse/RANGER-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Kumar updated RANGER-5499:
-----------------------------------
    Component/s: pdp
                     (was: kms)

> Support header based authentication
> -----------------------------------
>
>                 Key: RANGER-5499
>                 URL: https://issues.apache.org/jira/browse/RANGER-5499
>             Project: Ranger
>          Issue Type: New Feature
>          Components: admin, pdp
>            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)