[
https://issues.apache.org/jira/browse/NIFI-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444039#comment-17444039
]
David Handermann commented on NIFI-7835:
----------------------------------------
The custom SocketFactory implementation that NiFi uses when configuring the
SFTP connection does not currently pass the username and password properties
associated with the proxy service configuration. The SSHJ library relies on
standard Java proxy support, which makes it difficult to configure proxy
credentials for individual connections. Further evaluation is necessary to
implement a solution that works for SOCKS or HTTP proxies that require
authentication.
> SFTP processors (maybe other too) proxy doesn't use credentials
> ---------------------------------------------------------------
>
> Key: NIFI-7835
> URL: https://issues.apache.org/jira/browse/NIFI-7835
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.12.0, 1.11.4, 1.13.0, 1.12.1, 1.14.0, 1.13.1, 1.13.2,
> 1.15.0
> Environment: CentOS 7, Java 8 and 11, standalone Nifi
> Reporter: Wiktor Kubicki
> Priority: Major
>
> Hello,
> we tried use socks proxy configuration (with authorization) for
> listSFTP/fetchSFTP/getSFTP using processor configuration or Proxy
> Configuration Service. Each time we has got Getting java.net.SocketException:
> Malformed.
> We did tcp dump and saw, that the user/password is not provided - user is
> same as system user rather than this one from configuration.
> I've easly recreated issue on clean CentOS with java 8 and 11. Same problem
> was on NiFi 1.11.4 and 1.12.0.
> I think the problem is due of using sshj, but can be wrong. Very similar
> issue is https://issues.apache.org/jira/browse/NIFI-7749 - probably with the
> same cause.
>
> My workaround for sftp is using fuse-sftp and mount remote server as local
> share.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
