nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-4246) OAuth 2 Authorization support - Client Credentials Grant
Date Tue, 15 Aug 2017 00:43:00 GMT

    [ https://issues.apache.org/jira/browse/NIFI-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126681#comment-16126681
] 

ASF GitHub Bot commented on NIFI-4246:
--------------------------------------

GitHub user jdye64 opened a pull request:

    https://github.com/apache/nifi/pull/2085

    NIFI-4246 - Client Credentials Grant based OAuth2 Controller Service

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying
to resolve? Pay particular attention to the hyphen "-" character.
    
    - [X] Has your PR been rebased against the latest commit within the target branch (typically
master)?
    
    - [X] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check
clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [X] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?

    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file
under nifi-assembly?
    - [X] If applicable, have you updated the NOTICE file, including the main NOTICE file
found under nifi-assembly?
    - [X] If adding new Properties, have you added .displayName in addition to .name (programmatic
access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jdye64/nifi NIFI-4246

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2085.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2085
    
----
commit 6a63e544168f2db0059bab9b155ef9e3bd034531
Author: Jeremy Dyer <jeremydyer@apache.org>
Date:   2017-07-25T14:07:24Z

    NIFI-4246 - Client Credentials Grant based OAuth2 Controller Service

----


> 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
>
> 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
(v6.4.14#64029)

Mime
View raw message