FTP Export Account -> Secured Connection -> Case ref. 64254054 & 64049467

Hi Guys,

Hope you're doing well,

I am reaching out to follow up on our previous discussions about the SFTP integration with our client "Vorwerk". As you know, we've successfully secured the data import process. However, the data export is still being transmitted over an unsecured connection.

During our last conversation, which included Tom from the IT department, we recognized the need for additional development work on MintSoft's end to establish security for exports that is comparable to our import process.

Configuration set on 2Flow side:

we’re currently running 2 services for this connection:

1.The first service allows FTP to run using SSH on port 22. In this configuration, you should establish a secure SSH TCP tunnel and securely transfer encrypted data. This service is not related to FTPS and operates distinctly from port 21. However, Mintsoft has faced challenges connecting using this service.

2. The second service we utilize is FTPS, hosted by IIS. While this service indeed connects via port 21, But our server requires SSL/TLS encryption for this connection, ensuring the data remains encrypted and secure. This is the mechanism that Mintsoft employs to connect and transfer data to our server.

File path explanation:

-When Vorwerk tries to connect using SSH on port 22, it directs to the path: C:\2flowSftp\LocalUser\Vorwerk.

-However, when Mintsoft connects, it uses a separate FTPS service on port 21, which, thanks to our IIS setup, also maps to the same path: C:\2flowSftp\LocalUser\Vorwerk. (THIS IS WHERE WE ENCOUNTER ISSUES).

So, if you navigate to "Connect" -> "Order Integrations" -> "FTP import," you'll find an option to configure the "Encryption Mode." This setting allows us to establish a secure import connection.

However, if you go to "Connect" -> "Order Integrations" -> "FTP exports," you won't discover an option to adjust the "Encryption Mode" or any similar configurations. As a result, despite our attempts to implement a workaround, our configuration fails to secure the connection, leading to file exports being transmitted through an unsecure link.