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

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

Github user jugi92 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2018#discussion_r145136408
  
    --- Diff: 
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SFTPTransfer.java
 ---
    @@ -92,6 +93,39 @@
             .defaultValue("true")
             .required(true)
             .build();
    +    public static final PropertyDescriptor PROXY_HOST = new 
PropertyDescriptor.Builder()
    --- End diff --
    
    Hi,
    We would really like to see that the development goes into the direction 
that SOCKS Proxy with authentication will also be available.
    In many bigger companies it is a basic requirement and for us it is not 
possible to provide those parameters through the -D Options as mentioned in 
this comment: 
https://community.hortonworks.com/questions/30339/how-to-configure-proxy-server-details-with-user-an.html
    As JSCH offers all the possibilities and a reference implementation it 
should be possible to integrate it and broaden the functionality of Nifi and 
thus make it more attractive to companies.
    Please feel free to discuss my opinion.
    Best regards


> Add Proxy Properties to SFTP Processors
> ---------------------------------------
>
>                 Key: NIFI-4175
>                 URL: https://issues.apache.org/jira/browse/NIFI-4175
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Grant Langlois
>            Assignee: Andre F de Miranda
>            Priority: Minor
>
> Add proxy server configuration as properties to the Nifi SFTP components. 
> Specifically add properties for:
> Proxy Type: JSCH supported proxies including SOCKS4, SOCKS5 and HTTP
> Proxy Host
> Proxy Port
> Proxy Username
> Proxy Password
> This would allow these properties to be configured for each processor. These 
> properties would align with what is configurable for the JSCH session and 
> shouldn't require any additional dependencies.
> This proposal is similar to what is already implemented for the FTP processors



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to