====== SFTP send channel ======

The SFTP send channel allows the connection of a directory on a remote host via SFTP protocol.
Messages are stored in the directory stored in the channel from the message basket (outgoing) in the form of files.

==== Partner Address ====

You can use a partner address of type Ftp to define a sub path for a partner. The address must not start with a dot or with './'.

==== Properties ====

~~ GENERATED src="eBiss.Data.Resources.sFtpSendChannel" changed="" ~~
^Properties^^
^Name^Description^
|**Name**|The name of the channel|
|**Channel type name**|The Type of the channel|
|**Message direction**|For receive channels the direction of the received message (but require also for send channels)|
|**Message box**|The message box|
|**Public**|True if the channel should be visible in the sub node|
|**Host**|IP address of the sftp server |
|**Port**|SFTP Port, 22 by default|
|**Username**|Login to the SFTP directory.|
|**Password**|Password of the SFTP directory|
|**Output path**|Target path on the SFTP server|
|**Change logs**|The changes to the element are logged. The logging is activated in the [[en:hauptmenue:einstellungen:systemeinstellungen]], which is possible if a versioning license is available.|
^Properties (advanced)^^
^Name^Description^
|**Sender validation**|How the sender address should be validated|
|**Default sender**|The default sender|
|**Recipient validation**|How the recipient  address should be validated|
|**Default recipient**|The default recipient|
|**Immediate retries**|Retries, used by send channels. For some receive channels, the number of pickup attempts.|
|**Auto uncompress**|Check if receipt data are compressed and then uncompress them|
|**SFTP transfer mode**|Setting the transmission mode. Mode (Auto, Text, Binary) can be selected in the corresponding look main table.|
|**File name handling**|Here you can select a method to generate the filenames by means of a combo box.|
|**File exists handling**|Here you can select a file handling method from the combo box in case a file of the same name already exists in the directory. The file can be overwritten, documents attached to the file or parts of the file name can be renamed.|
|**Use temporary transport file name**|Specifies whether a different name is to be used for transferring the file. This option is activated by checking the checkbox.|
|**Temporary transport file name**|Setting a temporary file name for the transfer. The whole file name is specified, the default value is '_upload_.tmp', i.e. if 'Use temporary file name' is activated and no 'Temporary file name' has been stored, then the file name '_upload_.tmp' is used. After the successful transfer of the file, the file will be renamed to the actual filename.|
|**Timeout**|Specifies a time in seconds until a timeout occurs, , -1 stands for 60 minutes.|
|**Authentication certificate**|The private certificate((PFX file (PKCS #12, .pfx, .p12) and Open SSH certificates (.ppk) or in putty ppk format are recognized. If the certificate is not recognized please report to Pranke Support or read in using the following format: 'PEMKeyFile|<filename>', possible formats are: P7BFile, P7BBlob, SSHPublicKeyFile, PPKFile, PPKBlob, JKSFile, JKSBlob, PEMKeyFile, PEMKeyBlob, PublicKeyFile, PublicKeyBlob, SSHPublicKeyBlob)) of the client, if the authentication with the server should be done via the certificate.|
|**Auth. certificate password**|Password of the certificate specified in "Certificate for Authentication".|
|**Auth. certificate subject**|
|**Certificate info**|If a certificate has been stored and recognized, the FingerPrint, the serial number and the expiration date are displayed here.|
|**SSH encryption algorithms**|Encryption algorithms supported by this component for the encryption of the ssh session. Values can be entered as a comma separated list, using the following values: 'aes256-ctr, aes256-cbc, aes192-ctr, aes192-cbc, aes128-ctr, aes128-cbc, 3des-ctr, 3des-cbc, cast128-cbc, blowfish-cbc, arcfour, arcfour128, arcfour256, aes256-gcm@openssh.com, aes128-gcm@openssh.com'. By default this component supports 'aes256-cbc' and '3des-cbc'.|
|**SSH MAC algorithms**|MAC algorithms supported by this component for the ssh session. Values can be entered as a comma separated list, using the following values: 'hmac-sha1, hmac-md5, hmac-sha1-96, hmac-md5-96, hmac-sha2-256, hmac-sha2-256-96, hmac-sha2-512, hmac-sha2-512-96, hmac-ripemd160, hmac-ripemd160-96'. By default this component supports 'sha1', 'sha1-96', 'md5' and 'md5-96'.|
|**Additional SSH parameters**|This value is passed directly to the SSH component and should never be set. A case we know of is 'The server key seems to be invalid when using the 'diffie-hellman-group-exchange' key exchange algorithms' solved with the value: SSHKeyExchangeAlgorithms=ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521|