After refreshing a UAT environment's database from a PROD backup (a database clone), the SFTP Reader/Sender that was working fine before the clone can no longer authenticate to the SFTP server with its private key — even though the same key file still works fine when tested directly from the middle-tier host, and the reader/sender configuration was re-entered after the clone.

All FAQ questions / Integrations and APIs

Answer

Re-entering the existing SFTP reader/sender's configuration isn't enough after a database clone — delete the existing SFTP Reader and Sender instances entirely and recreate them from scratch instead; something about the reader/sender's internal state carried over from the source database doesn't reliably re-establish the connection even when every visible configuration field is re-set correctly. It's also worth exporting the tables holding your SFTP reader/sender configuration before a planned clone, so you have a reference to rebuild from quickly.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions