[ https://issues.apache.org/jira/browse/NIFI-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482003#comment-16482003 ]
ASF GitHub Bot commented on NIFI-4199: -------------------------------------- Github user MikeThomsen commented on the issue: https://github.com/apache/nifi/pull/2704 @ijokarumawak I'm going to start reviewing this. Once we get this done, I could use a hand with a review on [this](https://github.com/apache/nifi/pull/2723) lookup service I wrote which I'm partly holding back so I can do its proxy support via your changes here. > 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)