Using the SFTP (not to be confused with FTPS) protocol (see also http://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol) is very similar to FTP but there are some differences, most notable the options. If SFTP is used with private and/or public keys, the tagged value options on the deployment dependency must contain a string such as
Using the key pair myPrivateKey and myPublicKey allows you to access the server without having to authenticate the client (your E2E Bridge Service). The key files are uploaded to the resource repository using the E2E Bridge to upload mechanism. The key files are saved into the shared resources directory of the deployed service configuration.
Other supported SFTP options are:
|Pass one of the following literals:|
|Pass a String of 32 hexadecimal digits. The string should be the 128 bit MD5 checksum of the remote host's public key. The Bridge will reject the connection to the host unless the md5 sums match. This option refers only for scp and sftp transfers.|
|Password protecting the private key file|
Compared to FTP and FTPS, SFTP uses different commands. The following shows an extract of possible quote commands SFTP uses:
You can find a complete list of supported commands on the cURL haxx site.
Find below a list of relevant tagged values, if the URL adapter is used with the SFTP protocol.
Default values used when an option is not explicitly set are written in bold.
|method||SFTP method.||get, post, put, list|
|port||Machine port number the service is binding to. This port number can be given at service level only.|
|path||SFTP path for the SOAP request.|
|options||Native cURL options.||cURL Options|
|proxyType||Type of the proxy.||HTTP, SOCKS5|
|proxyURL||URL of the proxy server.|
|Upload failed, error message: ||The path is not correct.||In SFTP, the path has to be set absolutely or using the tilde ( ~ ) for the user home path, e.g. |