Settings

(1) Allowed sub types: Defines for which subtypes the channel may be used.

(2) Certificates: The corresponding certificates can be assigned here. Note: The assignment of certificates is only required if the Public Key Authentication is to be used instead of the login with ID/password. The actual transport encryption is carried out no matter if certificates are assigned to the channel.

(3) User directory (local): The home folder of the user of this SSH channel. See also (4).

(4) Do not create user directory again: If this checkbox is set, the user directory (and subdirectories, see "subdir.properties") is not created again when saving the channel. Note: The user directory is created when the channel is created, i.e. the first time it is saved. The checkbox is only visible if the channel already existed, i.e. not when it is created. If the checkmark is removed and the channel saved, the directory will be created again, but afterwards the checkmark will be set again automatically.

(5) Chroot: If this checkbox is set, the home directory is displayed as root directory during an SFTP session, i.e. you are then not in "/home/[username]", but in "/".

(6) Key type, Key fingerprint, Retrieve key: If the button "Retrieve key" is clicked, the connection to the partner system defined in field "Partner address" is established. The partner address must be specified in the form ssh://server:port. The port can be omitted if the server uses default port 22. The public key used for the SSH communication between Lobster Integration and the partner system is read, and the key type and key fingerprint fields are filled automatically.

(7) Define event exceptions: Opens a dialogue for editing the file ./etc/admin/datawizard/ftp_user_rules.properties. This file can be used to specify that all uploads of a specific user or even uploads to individual directories of a Lobster Integration user are not perceived as an event. The administrator is then responsible for copying/deleting the files. This setting is mainly relevant if a DMZ server is used.

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. Specifications like "dir4/Orders*" are not possible.

(8) Access rights: The access rights are managed in the same way as with FTP channels.

(9) Whitelist, Blacklist: Enables the explicit enabling (whitelist) and disabling (blacklist) of certain client IPs/URLs. Both the whitelist and blacklist are evaluated. If an address is present on both lists, the blacklist takes precedence.

(10) Filename charset: The encoding used to interpret the name of a received file. Default: "UTF-8".