Issue with IFS Connect SFTP Upload – Rename Operation Potentially Causing Connection Block by Bank SFTP Server

Has anyone else experienced this behavior with IFS Connect and SFTP?

Yes, just got off a call with local bank among “the big 4” and they considers any file name change from .xml.part to .xml a potential file content tampering i.e. the file needs to ‘arrive’ with final file extension .xml.

Hi ​@InfKristN 

Glad to hear from you after some time :)

Yes, we faced the same issue with bank SFTPs. One solution is to ask the bank for a temp directory and then use that as TEMP_DIRECTORY in the sftp sender. If this doesn’t work, unfortunately  you need to make a workaround outside IFS such as save the file to a different location, build something to poll the location, and send the file to the bank sftp.

Back in the days, I used to achieve this using a windows scheduler script and WinScp cmd, but now you can build a modern solution like a azure logic app with SFTP connector.

Hope it helps!

Damith

I have worked a case on this topic in early 2025 where an IFS customer needed to send a file to a 3rd party financial institution….and the financial institution wouldn’t allow file renaming upon receipt.

The case was thoroughly examined by multiple IFS managers in the Support and R&D areas.  After multiple exchanges of phone calls and correspondence a senior manager with responsibility for direction of development replied IFS would NOT be making changes to its policy of file renaming upon sending to a 3rd party, regardless of that 3rd party’s internal security policies.

I got to deliver this information to the IFS customer contacts after receipt of that correspondence.

Note that it could be possible to request a customization from IFS to allow for the file renaming behavior to be suppressed.  But this would need to be done on a billable basis if the correct resources within IFS (or a qualified partner) could be identified and their help be obtained.