You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Anil Rai <an...@gmail.com> on 2018/06/04 18:11:55 UTC
oAuth for API stood up on nifi
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
Posted by Anil Rai <an...@gmail.com>.
Thanks Bryan.
On Mon, Jun 4, 2018 at 2:34 PM, Bryan Bende <bb...@gmail.com> 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 <an...@gmail.com> 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
Posted by Bryan Bende <bb...@gmail.com>.
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 <an...@gmail.com> 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