Ftp File Store
Description | An FTP(S) server to manage files |
---|---|
Type | ftp |
Category | File |
TLS support
Due to poor support of TLS client session resumption in the .NET framework (and others), which is mandated by many FTPS servers, only the control channel (logins/ file names / file modes) is encrypted. This is compatible with PureFtpd's --tls=2 option which is what we deploy. But the data channel will remain unencrypted. Ideally switch to SFTP or S3 on the internet.
No verification of the server certificates is performed. Ideally switch to SFTP or S3 on the internet.
Configuration
Name | Description | Type | Mandatory | Comment |
---|---|---|---|---|
HostName | Host address of the FTP(S) | string | TRUE | |
Port | Port of the FTP(S) | int | TRUE | |
Username | The user used to connect to the FTP | string | TRUE | |
Password | The password of the user to connect to the FTP | string | TRUE | |
BasePath | The base directory on the FTP server | string | TRUE | |
UseTls | Should the store use TLS | bool | TRUE | |
EncryptionMode | Choose FTP connection mode
| string | FALSE | Defaults to "Auto" |
SslProtocols | Select allowed protocols in:
| string array | FALSE | Defaults to "Tls12" |
DataConnectionEncryption | Data connection must be encrypted or not | Boolean | FALSE | default to FALSE and is not supported by dfakto ftp server right now (see remark above) Available since version 1.4.14 |
{
"Name": "ftp-server",
"Type": "ftp",
"HealthCheck": true,
"Config": {
"HostName": "ftp.dfakto.com",
"Port": "21",
"Username": "username",
"Password": "password",
"BasePath": "/",
"UseTls": "true"
}
}