[jira] [Resolved] (NIFI-4243) OAuth 2 Authorization support - Authorization Code Grant

["David Handermann (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Handermann resolved NIFI-4243.
------------------------------------
    Resolution: Won't Fix

The Authorization Code Grant Type is designed for interactive authentication with a user, not for automated communication. The Standard OAuth2 Service provides support for the Client Credentials Grant Type, which is the standard approach for programmatic access. Although it might be possible to implementation Authorization Code Grant Type handling with a custom UI, the token expiration would not support persistent programmatic access.

> OAuth 2 Authorization support - Authorization Code Grant 
> ---------------------------------------------------------
>
>                 Key: NIFI-4243
>                 URL: https://issues.apache.org/jira/browse/NIFI-4243
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: 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 Authorization Code Grant method defined at https://tools.ietf.org/html/rfc6749#section-4.1
> 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 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
(v8.20.10#820010)