The issue with FTP and self-service deployments

Even though using FTP or SFTP servers when building integrations might seem a bit outdated, it’s a common scenario. Many third parties, especially banks, still use them to distribute information instead of building APIs.

In the past, we could create this integration using X++ and some .NET to connect to an FTP server and operate it. Similarly, for an SFTP server, we used SSH.NET.

However, some issues tended to appear after the change to the new self-service deployments, which moved the infrastructure from a classic monolithic architecture to a container-based one. The authentication request sent from F&O to the FTP server could have a different IP address than the request to access a file or folder, and an error would occur, breaking the integration.

Note

If you develop a solution to connect to an FTP server using X++ and test it successfully in a development environment, you must know that there’s no guarantee...