nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-4246) OAuth 2 Authorization support - Client Credentials Grant
Date Sat, 26 Aug 2017 13:53:02 GMT


ASF GitHub Bot commented on NIFI-4246:

Github user jdye64 commented on the issue:
    @alopresto I tested it against tubemogl [1] and freewheel [2]. I obviously can't share
those sensitive credentials here but would something like suffice?

    [1] -
    [2] - 

> OAuth 2 Authorization support - Client Credentials Grant
> --------------------------------------------------------
>                 Key: NIFI-4246
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Jeremy Dyer
>            Assignee: Jeremy Dyer
> If your interacting with REST endpoints on the web chances are you are going to run into
an OAuth2 secured webservice. The IETF (Internet Engineering Task Force) defines 4 methods
in which OAuth2 authorization can occur. This JIRA is focused solely on the Client Credentials
Grant method defined at
> This implementation should provide a ControllerService in which the enduser can configure
the credentials for obtaining the authorization grant (access token) from the resource owner.
In turn a new property will be added to the InvokeHTTP processor (if it doesn't already exist
from one of the other JIRA efforts similar to this one) where the processor can reference
this controller service to obtain the access token and insert the appropriate HTTP header
(Authorization: Bearer{access_token}) so that the InvokeHTTP processor can interact with the
OAuth protected resources without having to worry about setting up the credentials for each
InvokeHTTP processor saving time and complexity.

This message was sent by Atlassian JIRA

View raw message