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

Abhishek Kumar resolved RANGER-5550.
------------------------------------
    Fix Version/s: 3.0.0
                   2.9.0
       Resolution: Fixed

Merged in master: 
[https://github.com/apache/ranger/commit/e8f8063f69bdf64533677ddd5e1380a6de6c9d80]

Merged in ranger-2.9: 
[https://github.com/apache/ranger/commit/e6f6f640a3f55ecedd2f39ca4323877b23e5dbe2]
 

> introduce authz-remote library to support thin client integration for plugins
> -----------------------------------------------------------------------------
>
>                 Key: RANGER-5550
>                 URL: https://issues.apache.org/jira/browse/RANGER-5550
>             Project: Ranger
>          Issue Type: New Feature
>          Components: authz-api, pdp
>            Reporter: Madhan Neethiraj
>            Assignee: Abhishek Kumar
>            Priority: Major
>             Fix For: 3.0.0, 2.9.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Ranger plugins use {{authz-embedded}} or {{ranger-plugins-common}} library to 
> evaluate Ranger policies to authorize access requests. These libraries run 
> the policy engine in-process, making the policy evaluation very responsive. 
> However, they do bring in a long list of dependent libraries including 
> jackson, jetty, httpcomponents, solrj, zookeeper, hadoop-client, dropwizard, 
> graalvm, and more.
> For plugins where a minimal library dependency is preferred, Ranger should 
> offer integration approach where policy evaluation is performed 
> out-of-process, in {{ranger-pdp}} server introduced in RANGER-5263. This Jira 
> tracks new Ranger library, {{authz-remote}} that provides implementation of 
> RangerAuthorizer interface that calls {{ranger-pdp}} REST APIs to evaluate 
> policies. It is critical for this module to keeps it dependency list to as 
> minimal as possible.



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

Reply via email to