OFTP2

Secure B2B file exchange over OFTP2: send and collect files with signed delivery receipts

Signs in with: Connection details
Runs on: Cloud or On-Prem Worker
Operations: 7
Ready-made triggers: 0

Connect OFTP2

In Neblex open Connect › Connections and click New Connection.
Search for OFTP2 and give the connection a clear name.
Fill in the fields. Secret values are encrypted and never shown again.
Click Test, then Create Connection.

If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.

Field	What to enter
Partner hostRequired	The partner's OFTP2 server, for example oftp.partner.example.
PortOptional	Leave empty for 6619 with TLS or 3305 without.
Use TLSOptional	ODETTE-FTP over TLS (odette-ftps). Turn off only for private networks.
Private CA certificate (PEM)OptionalSecret	For a partner server certificate issued by a private CA.
Present our certificate in TLSOptional	Authenticate to the partner's TLS server with our certificate.
Our ODETTE IDRequired	Our identification code (SSID), for example O0013000000ACME.
Our passwordOptionalSecret	The password we present to the partner.
Partner ODETTE IDRequired	The identification code the partner must present.
Partner passwordOptionalSecret	The password the partner must present. Leave empty to accept any.
Session user dataOptional	Up to 8 characters agreed with the partner.
Our certificate (PEM)Optional	The certificate the partner registered for us.
Our private key (PKCS#8 PEM)OptionalSecret	Decrypts files and challenges sent to us and signs files and responses.
Partner certificate (PEM)Optional	Encrypts files and challenges for the partner and verifies its signatures.
Secure authenticationOptional	Prove both identities with certificate challenges when the session starts. Both sides must agree.
Cipher suiteOptional	Used to encrypt and sign files and challenges, as agreed with the partner.
Exchange buffer sizeOptional	Largest data buffer in octets (128 to 99999). Leave empty to offer the maximum; the smaller of both sides is used.
Credit windowOptional	Buffers sent before the receiver confirms (1 to 999). Leave empty to offer the maximum; the smaller of both sides is used.
Buffer compressionOptional	Compress repeated bytes in data buffers when the partner supports it.
Sign filesOptional	Sign sent files unless a step says otherwise.
Encrypt filesOptional	Encrypt sent files unless a step says otherwise.
Compress filesOptional	Compress sent files unless a step says otherwise.
Ask for signed EERPsOptional	Ask partners to sign their end-to-end responses unless a step says otherwise.

Use it in a flow

Open a flow, open the node library and search for OFTP2.
Drag it onto the canvas and choose an Operation and your connection.
Map the operation's fields from earlier steps, or click Map with Matt.
Use Test this step to see what it returns, then save.

To start a flow from OFTP2 without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if OFTP2 can send webhooks, a Webhook trigger receives them at its own URL.

Operations

7 operations in 3 groups. Each one is a step you can add to a flow.

Connection1

Test the connectionping Open a session with the partner: TLS, identification, password and secure authentication when configured.

Files4

Collect files`receiveFiles`		Hand the turn to the partner and take every file it holds for us, stored as files, with the responses it sends.
Open a file`openFile`		Decrypt, decompress and verify a received CMS envelope into the original file.
Prepare a file`prepareFile`		Sign, compress and encrypt a file into a CMS envelope ready to send, so a restarted transfer sends exactly the same bytes.
Send a file`sendFile`		Send each input's file as a virtual file in one session, with optional signing, compression and encryption and restart from the partner's position.

Responses2

Send a NERP`sendNerp`		Tell the originator that a file could not be delivered or processed (Negative End Response), with the reason.
Send an EERP`sendEerp`		Confirm to the originator that a received file reached its final recipient (End to End Response), signed when asked.