*Wednesday, January 16, 2019 at 12:21 AM
*To: *
*Subject: *Re: How to extend the authorization engine in order to use
an external service
Hi,
just to clarify my question: the plugin I would like to build should
make the call to the external service and then use the obtained data
as a preli
bstracted, so you will have to walk through all the code path and
put enough debug statements to understand it.
Bosco
*From: *Matteo Alessandroni
*Reply-To: *
*Date: *Wednesday, January 16, 2019 at 12:21 AM
*To: *
*Subject: *Re: How to extend the authorization engine in order to use
an externa
understand it.
Bosco
From: Matteo Alessandroni
Reply-To:
Date: Wednesday, January 16, 2019 at 12:21 AM
To:
Subject: Re: How to extend the authorization engine in order to use an external
service
Hi,
just to clarify my question: the plugin I would like to build should make the
call
Hi,
just to clarify my question: the plugin I would like to build should
make the call to the external service and then use the obtained data as
a preliminary authorization check to use then with services like HDFS,
HBASE, HIVE. In my case Apache Ranger is already integrated to those
services
Hi Bosco,
On 15/01/19 12:41, Don Bosco Durai wrote:
Matteo
Are you extending current plugin or creating brand new custom plugin
for another component?
Actually I'm not sure whether I need to extend an existing plugin or
create a new brand one.
I will use Apache Ranger to provide runtime
Matteo
Are you extending current plugin or creating brand new custom plugin for
another component?
If it current plugin, then Ranger has a design where you can enrich the context
and use it in condition. IP based and most internal extensions uses that design
pattern. The Policy side, you
