Overview
Contains multiple Smart Services for interacting with a remote file server via SFTP, FTP, or SCP. Using these services, an Appian application can be configured to send and receive files, folders, and metadata in a process. Features support for zlib compression.
Key Features & Functionality
Smart Services included:
All smart services in the package use Secure Credentials Store.
SFTP send file smartservice> Remote File Path input parameter expects the complete file path, inluding the name of the file, which you are passing in the source document parameter. Use document() function to get the name and file extension of the source document to append it to the Remote File Path
We upgraded the plugin to 4.1.0 and while using the latest smart service '(SFTP) Get Remote folder Contents' replacing the deprecated smart service "Get Remote Directory Contents over SFTP", we got the below error:
"Algorithm negotiation fail: algorithmName=""server_host_key"" jschProposal=""ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256"" serverProposal=""ssh-rsa"""
The same smart service (SFTP) Get Remote Folder Contents works fine with the Plugin version 3.0.3.
Is there a know resolution to this error?
While receiving file using smart service "Receive File Over SFTP", I am getting error as "Error copying the remote file to disk. See application server log for more details. Error Message: The message [filename] is not extractable!". It worked fist time and from 2nd time I am getting error. Also I tried next day but still getting same error.
I am using plugin with version 2.2.1.
Can you please suggest solution on this?
We are using the SFTP plugin and upgraded to V4.0.0.From our health check report, we are getting the below warning with Medium risk.
Warning: Plug-ins using removed, private or deprecated Appian APIs
Message: com.appiancorp.a2.process.runtime.activities.sftp
Description:
Can we update this plugin to be RFC compliant as it's currently not. This has become a security concern for us.
SolarWinds highly recommends that the customer strategize and adjust their infrastructure to adhere to RFC standards and utilize clients that are up to date, as detailed in the article Resolution 2
https://support.solarwinds.com/SuccessCenter/s/article/SFTP-connection-not-established-for-legacy-Java-clients?language=en_US.
Hello,
Same configuration, (Username password ppk) WORKS FINE with Get Remote Directory Contents Over SFTP which is deprecatedHowever, I try to access the content using new smart service available in 3.xx with same configuration it gives me and error Invalid keystore format . I tried all formats ppk pem ssh
Any suggestions Thank you
We have been having the same issues with our connectivity to a new SFTP service. What we have found is the new SFTP service is using newer cyphers and which Appian SFTP plugin v3.0.3 does not support.