Versions Compared

Old Version 18

changes.mady.by.user Matt Walkenhorst

Saved on

compared with

New Version Current

changes.mady.by.user Dennis Navarro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
panelIconId1f5a5
panelIcon:desktop:
panelIconText🖥️
bgColor#998DD9

We prefer the sending postback files via SFTP or HTTP POST over TLS (https)

Here are the methods we support

Table of Contents

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FF8F73

Passwords and Authentication Tokens must not be provided in plain text. Please use a tool like pwpush.com

SFTP

Two types of SFTP is supported:

Pros

Cons

  • Best for your ERP/WMS to receive the files in your environment

Robust as SFTP protocols support validation of delivery

  • Reliable transfer

  • Encrypted files

  • Authenticated transfer

  • Hosting of SFTP server

Details Required

  • Host

  • Port

  • Username

  • Password

  • Static External IPs used to connect to be added to the allow-lilst

  • Our environment will save the private key provided by your SFTP server in the initial login and use it in subsequent authentications.

...

  • or Public key of the server

  • Allow list our outgoing SFTP server IP Allowlisting EFM URLs & IP Addresses

  • Provide the fingerprint of the public key, as we use that to validate that we are connecting to the correct server.

HTTP POST

We can send XML data to an API endpoint but it is a one way transaction of data, we do not match and find references to reconcile the consignment details to.

Pros

Cons

  • Secure transmission of file

Configuration of an API endpoint required

  • Reliable transfer

Must be able to configure an authenticated API client

Details Required

  • HTTPS Endpoint only

  • Subdirectory (if relevantEFM specific authentication (ie no unauthenticated endpoints)

FTP (TLS ONLY if SFTP is not an option)

Pros

Cons

  • Suitable if you cannot setup an SFTP server

  • The file is not encrypted when sent across

    • The file can be intercepted easily

    • or HTTP POST

    • When certificate changes, failures in transmission can occur

    • Unforseen errors can cause files to fail to send

    Details Required

    • Host

    • Username

    • Password

    • Port

    Email - Legacy

    We are able to send postback files to email addresses. Please see Postback - Email (Legacy Option) for more details.

    Pros

    Cons

    • Suitable if you cannot setup an SFTP server

    • We cannot validate delivery of the file

    • If a receiver of the report leaves your organisation, the

    fail

    • mail may end up

    in a black hole

    • not being delivered.

    Details Required

    • Email address