Introduction: OFTP with Lobster_data.

See also: General Channel Settings, OFTP (Input Agent), OFTP (Input Agent Cron) and Response Route OFTP.

(1) Specifies for which subtype the channel may be used.

• OFTP via ISDN.

• OFTP via TCP/IP.

• OFTP via TLS .

(2) Here the local certificate (with private key) is assigned. Only needed for OFTP2 to decrypt received encrypted files and to sign sent files. For OFTP2 via TLS (1), a client certificate for the TLS connection may additionally be required for outgoing connections. The local certificate will also be used for that.

In addition, the partner certificate is assigned here, i.e. the public part of the certificate of the partner to which the channel is assigned. Only needed for OFTP2 to encrypt sent files and to check received signed files.

(3) Should your local certificate or the partner certificate expire soon and you already have a corresponding new certificate, then you can add the new certificate here. Once the old certificate has expired, then the pending certificate is used.

(4) Specifies whether files are to be signed or encrypted when sent to the partner system. The files are signed with the signature algorithm set in (10) and the local certificate (2). The files are encrypted using the encryption algorithm set in (12) with the partner certificate (2).

(5) If the checkbox Receive signed is set, an error is generated if the received files are not signed and the files are rejected. If the checkbox Receive encrypted is set, an error is generated if the received files are not encrypted and the files are rejected.

(6) The OFTP restart functionality can be suppressed.

(7) If set, the partner requires signed receipt confirmations (EERPs, End to End Responses) for outgoing data transmissions to the partner.

(8) If this checkbox is set then only files with an additional SFID combination listed in (20) will be accepted, otherwise they will be rejected.

(9) Must be set if the automatic certificate exchange is to be used. See the corresponding section below.

(10) Determines the algorithm with which sent files are signed. The setting only works if the checkbox Send signed (4) is set.

(11) SecAuth is an authentication by client certificate. The local certificate (2) is used for that, comparable to the pubkey authentication with SSH.

(12) Determines the algorithm with which sent files are encrypted. The setting only works if the checkbox Send encrypted (4) is set.

Note: The signature and encryption algorithm specified by the partner should always be explicitly set to avoid problems in case Odette specifies a new default value.

(13) The directory, in which the received files or the files to be sent are stored. See also section Home Folders.

(14) The ISDN number under which Lobster_data/the partner system receives data via OFTP.

(15) The X.25 address under which Lobster_data/the partner system receives data via OFTP.

(16) Input field for the subject of the X.509 certificate to detect incoming partner certificates during the automated certificate exchange, e.g. *CN=OFTP2FIRMAX* or *CN=aaaa*. See the corresponding section below.

(17) Here, the name of the ODETTE TSL list is expected. This is the name of an ODETTE-maintained list of allowed certification authorities (CAs) to be accepted for automated certificate exchange. Practically, the value will always be OFTP2.

(18) The TLS encryption algorithm. This value should only be set to resolve TLS handshake issues.

(19) Here, the value can be set to 0 in virtually all cases (Credit Count, X.25 Window size, Exchange Buffer). Should other values be necessary in rare cases, please contact our support.

(20) See section Additional certificates/SFIDs below.

(21) An attempt is made to send a file TEST with the content TEST to the configured partner.

(22) Starts the pickup test (in the background) for the configured partner.

Note: The tests (14) and (15) always refer to the stored channel. Please save the channel before the test if you have made any changes.