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

Madhan Neethiraj updated RANGER-5263:
-------------------------------------
    Summary: Ranger policy-decision-point (PDP) service  (was: Ranger 
policy-decision-point (PDP) server)

> Ranger policy-decision-point (PDP) service
> ------------------------------------------
>
>                 Key: RANGER-5263
>                 URL: https://issues.apache.org/jira/browse/RANGER-5263
>             Project: Ranger
>          Issue Type: New Feature
>          Components: Ranger
>            Reporter: Madhan Neethiraj
>            Priority: Major
>
> Apache Ranger enables centralized management of authorization policies for 
> data in a wide variety of services, including file systems, databases, data 
> streams, search indexes, schema registries, metadata services and APIs.
> Apache Ranger APIs and UI for policy management are available out-of-the-box, 
> enabling enterprises to use a common policy model to setup authorization 
> policies across their data estate.
> Apache Ranger provides Java libraries for services build to authorization 
> plugins. Authorization plugins for several popular services are available 
> out-of-the-box from Apache Ranger; more authorization plugin implementations 
> are available from other open-source projects as well like Trino, NiFi, Kudu.
>  
> To address needs of services where Java based authorization plugin is not 
> feasible, Apache Ranger should provide a service having REST API endpoints 
> that authorize access requests by evaluating policies setup in Apache Ranger. 
> These REST APIs will enable services implemented using a wider variety of 
> technologies (like Go, Python, .NET, Rust) to authorize resource accesses 
> using Apache Ranger policies. In addition to extending Apache Ranger to 
> larger number of services, this approach can also simplify integration with 
> fewer configurations and dependencies for service implemented in Java as well.



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

Reply via email to