Re: oAuth for API stood up on nifi

[Anil Rai]

Thanks Bryan.

On Mon, Jun 4, 2018 at 2:34 PM, Bryan Bende  wrote:

> Hello,
>
> Processors can't leverage NiFi's internal authentication and
> authorization mechanisms.
>
> For HandleHttpRequest it supports two-way TLS for client authentication.
>
> -Bryan
>
>
> On Mon, Jun 4, 2018 at 2:11 PM, Anil Rai  wrote:
> > Team, for invoking the nifi API's on a secured cluster, we have to get
> the
> > token and then invoke.
> > Now if I stand up a new API via HandleHttpRequest processor, is there a
> way
> > to use the inbuilt oAuth to access this API?
> >
> > Regards
> > Anil
>

Re: oAuth for API stood up on nifi

[Bryan Bende]

Hello,

Processors can't leverage NiFi's internal authentication and
authorization mechanisms.

For HandleHttpRequest it supports two-way TLS for client authentication.

-Bryan


On Mon, Jun 4, 2018 at 2:11 PM, Anil Rai  wrote:
> Team, for invoking the nifi API's on a secured cluster, we have to get the
> token and then invoke.
> Now if I stand up a new API via HandleHttpRequest processor, is there a way
> to use the inbuilt oAuth to access this API?
>
> Regards
> Anil

oAuth for API stood up on nifi

[Anil Rai]

Team, for invoking the nifi API's on a secured cluster, we have to get the
token and then invoke.
Now if I stand up a new API via HandleHttpRequest processor, is there a way
to use the inbuilt oAuth to access this API?

Regards
Anil