[ https://issues.apache.org/jira/browse/NIFI-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482052#comment-16482052 ]
ASF subversion and git services commented on NIFI-4199: ------------------------------------------------------- Commit 2834fa4ce477014dfad8c96b6d326d0f1f06a23e in nifi's branch refs/heads/master from [~ijokarumawak] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2834fa4 ] NIFI-4199: Added ProxyConfigurationService - Added ProxyConfigurationService to manage centralized proxy configurations - Adopt ProxyConfigurationService at FTP and HTTP processors NIFI-4175 - Add HTTP proxy support to *SFTP processors This closes #2018. Signed-off-by: Koji Kawamura <ijokaruma...@apache.org> NIFI-4199: Add ProxyConfigurationService to SFTP processors - Fixed check style issue - Use the same proxy related PropertyDescriptors from FTPTransfer and SFTPTransfer - Dropped FlowFile EL evaluation support to make it align with other processors spec, Now it supports VARIABLE_REGISTRY - Added ProxyConfigurationService to SFTP processors - Added SOCKS proxy support to SFTP processors NIFI-4199: Added ProxyConfigurationService to ElasticsearchHttp processors - ElasticsearchHttp processors now support SOCKS proxy, too - Added proxy support to PutElasticsearchHttpRecord - Moved more common property descriptors to AbstractElasticsearchHttpProcessor and just return static unmodifiable property descriptor list at each implementation processors NIFI-4196 - Expose AWS proxy authentication settings NIFI-4196 - Fix jUnit errors This closes #2016. Signed-off-by: Koji Kawamura <ijokaruma...@apache.org> NIFI-4199: Add ProxyConfigService to AWS processors - Applied ProxyConfigService to S3 processors - Added proxy support to following processors: - PutKinesisFirehose, PutKinesisStream - PutDynamoDB, DeleteDynamoDB, GetDynamoDB - PutKinesisStream - All AWS processors support HTTP proxy now NIFI-4199: Add ProxyConfigService to Azure processors NIFI-4199: More explicit validation and docs for Proxy spec - Each processor has different supporting Proxy specs - Show supported spec to ProxyConfigurationService property doc - Validate not only Proxy type, but also with Authentication NIFI-4199: Incorporated review comments - Fixed TestListS3 property descriptor check - Separate name and displayName This closes #2016 This closes #2018 This closes #2704 Signed-off-by: Mike Thomsen <mikerthom...@gmail.com> > 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)