SSH (Channel Settings)
See also: General Channel Settings, SSH (Input Agent), SSH/SCP (Input Agent Cron) and Response Route SCP.
(1) Defines for which subtypes the channel may be used. The subtypes SCP (Secure Copy) and SFTP (SSH File Transfer Protocol) are available.
(2) 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) The home folder of the user of this SSH channel.
(4) If the button Retrieve key is clicked, the connection to the partner system defined in the partner address field 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_data and the partner system is read, and the key type and key fingerprint fields are filled automatically.
(5) 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_data 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.
#Sample for user ftp (to be excluded entirely)
ftp
#Sample for user ftp, exclude path "dir1", "dir2" and "dir3/sub" under home of user
ftp=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.
(6) The access rights are managed in the same way as with FTP channels.