You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Madhan Neethiraj (Jira)" <ji...@apache.org> on 2022/08/12 16:59:00 UTC

[jira] [Updated] (RANGER-3856) Ranger admin client option to work with non-kerberized server

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

Madhan Neethiraj updated RANGER-3856:
-------------------------------------
    Attachment: RANGER-3856.patch

> Ranger admin client option to work with non-kerberized server
> -------------------------------------------------------------
>
>                 Key: RANGER-3856
>                 URL: https://issues.apache.org/jira/browse/RANGER-3856
>             Project: Ranger
>          Issue Type: Improvement
>          Components: plugins
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>         Attachments: RANGER-3856.patch
>
>
> Ranger plugins use RangerAdminClient implementation to call Ranger admin REST APIs, for example to download policies. These implementations use local hadoop configuration to determine whether to use Kerberos authentication or not. To address deployment scenarios that run plugins in Kerberos environment and Ranger admin server in non-kerberized environment, it will help to have an option to force RangerAdminClient to operate in non-kerberos mode.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)