You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2018/05/15 07:28:00 UTC

[jira] [Updated] (NIFI-4199) NiFi processors should be able to share proxy settings

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

Koji Kawamura updated NIFI-4199:
--------------------------------
    Status: Patch Available  (was: In Progress)

A PullRequest is ready for review. The PR includes following changes:
* Added ProxyConfigurationService to manage centralized proxy configurations
* Adopt ProxyConfigurationService at FTP and HTTP processors

Only FTP and HTTP processors are updated as the base improvement. Once this gets merged we can expand the same approach to broader processors.


> NiFi processors should be able to share proxy settings
> ------------------------------------------------------
>
>                 Key: NIFI-4199
>                 URL: https://issues.apache.org/jira/browse/NIFI-4199
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Andre F de Miranda
>            Assignee: Koji Kawamura
>            Priority: Major
>
> Currently, configuring proxy settings for NiFi processors may be a tedious process that requires the DFM to set proxy settings on individual processors. 
> This leads to:
> * Duplication of work
> * Management overhead (as password must be changed on multiple locations)
> * Lower security (as proxy credentials must be known by "n" DFMs)
> Ideally, NiFi should offer a way to minimise duplication of work by offering a something similar to the Standard SSL Context services. This way, the DFM could set the proxy settings once an all authorised users could tap into those settings.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)