FTP (Channel Settings)
Introduction: Lobster_data as FTP Server.
See also: General Channel Settings, FTP (Input Agent), FTP (Input Agent Cron) and Response Route FTP.
(1) Allowed subtypes are 'normal' FTP and implicit and explicit FTPS. FTPS is an extension of FTP that also provides encryption over TLS and SSL for security. Implicit and explicit are two different methods of how to establish these additional layers of security during connection setup. Details can be found here. If one of the two FTPS options is selected, certificates for encryption can be selected in further fields (Local Certificates and Partner Certificates).
(2) The user directory (or home folder) of the user of this FTP channel.
(3) If this checkbox is set, the user cannot change to a directory outside (i.e. above) of the home folder. This is the default setting. The setting should only be changed in justified exceptional cases. In the current implementation of the FTP server, it is not possible to change to a directory outside of the home folder anyway. However, if the basis of the implementation changes in the future, this might no longer be ensured, so this setting is available.
(4) This option may enhance performance if it prevents multiple SSH connection setups.
(5) Tests if the outgoing FTP connection can be established.
(6) Opens a dialogue for editing the file ./etc/admin/datawizard/ftp_user_rules.properties. In this file, you can specify that all uploads of a given user or even uploads to individual directories of a user are not perceived as an event. The administrator is then responsible for copying/deleting the files. This setting is especially relevant for the operation of a DMZ server.
#Sample for user ftp (to be excluded entirely)ftp#Sample for user ftp, exclude path "dir1", "dir2" and "dir3/sub" under home of userftp=dir1;dir2;dir3/sub;dir4/*Notes:
If there is only a username specified in a line, all events for this user are excluded.
If directories are specified, no placeholders or regular expressions are allowed. The only exception is * (see next note).
If a directory is specified, exclusions of events apply only to this directory, not to its subdirectories. But if * is used, all subdirectories are excluded. For dir4/* that is dir4/sub1 and also dir4/sub2, as well as dir4/sub2/sub3, etc. Note: Specifications like dir4/Orders* are not possible.
Access Rights
The access rights for the user can optionally be managed here. The rights to read, write, create and delete files and folders can be assigned. The specification of the path is always relative to the home folder (see item (2) in the first screenshot).
Note: The user rights that are defined here refer to the user of our FTP server that is defined on page Partner Access (partner to you).
Note on the Order of Access Rights
Regardless of the order in which the rules are generated and stored, internally, they will be sorted alphabetically in descending order, as you can see in the screenshot above. This is because the first matching rule in the list is used to read the access rights of a user to a particular folder.
So if a user were in the subfolder /ftp/in of the user home folder and the first rule in the list would be /ftp, then this rule would be used. If the rule / was the first in the list, then it would be used. Sorting thus ensures that always the most specific available rule is used. If that were not the case and the rule / would be the first in the list, then only this rule would be used and never any others.