[
https://issues.apache.org/jira/browse/NIFI-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546877#comment-16546877
]
ASF GitHub Bot commented on NIFI-4246:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2901
Hi @jasonrogena . Thanks for submitting this. I'm sure @jdye64 appreciates
it as well because I know he is busy but wants this feature incorporated. I am
a little busy with some other things right now but I will definitely take a
look at this.
A couple quick suggestions I know I will have:
* Some of your files still reference NiFi `1.5.0-SNAPSHOT` or `1.6.0`.
Others correctly reference `1.8.0-SNAPSHOT` as the current development version.
Please ensure that all development versions are `1.8.0-SNAPSHOT`, and the
latest released version at this time is `1.7.1`.
* Some files have the license text block after package declarations,
imports, or XML opening tags. In each of these files, it needs to be the very
first block of text. You can identify issues by running the maven build with
`-Pcontrib-check` and it will highlight these issues for you. This will also
run the NiFi checkstyle rules to help identify any code style issues. If you
have issues with binary files being caught, you can exclude them in the
`pom.xml` (search the project for `<excludes combine.children="append">` in
other `pom.xml` files for examples).
> OAuth 2 Authorization support - Client Credentials Grant
> --------------------------------------------------------
>
> Key: NIFI-4246
> URL: https://issues.apache.org/jira/browse/NIFI-4246
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
> Priority: Major
>
> 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
> https://tools.ietf.org/html/rfc6749#section-4.4
> 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
(v7.6.3#76005)
