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

David Handermann commented on NIFI-7749:
----------------------------------------

The change from JSch to SSHJ in NiFi 1.10.0 for NIFI-5816 apparently broke 
support for authenticated HTTPS and SOCKS proxies.  JSch included custom code 
to handle proxy authentication for each connection, but the current 
implementation does not handle passing proxy credentials.

> ListSFTP Failure using Authenticated HTTPS Proxy
> ------------------------------------------------
>
>                 Key: NIFI-7749
>                 URL: https://issues.apache.org/jira/browse/NIFI-7749
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.11.4
>         Environment: Windows 10 + Java8 + One standalone NIFI
>            Reporter: Mermillod
>            Assignee: David Handermann
>            Priority: Major
>         Attachments: listSFTP.xml
>
>
> Connecting to a B2B SFTP over HTTPs proxy : 
>  
> ListSFTP[id=9e4976a8-7457-3ded-7ddd-28cbf73202c8] 
> ListSFTP[id=9e4976a8-7457-3ded-7ddd-28cbf73202c8] failed to process session 
> due to {color:#FF0000}Should not reach here{color}; Processor 
> Administratively Yielded for 1 sec: java.lang.InternalError: Should not reach 
> here
>  
> I cant find a clue in github for the keyword "Should not reach here". 
> Template with "masked" URLs/credentials.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to