Version 6.3.1 (Beta)

Applicability Statement 4 (AS4)

  • Added support for the Applicability Statement 4 (AS4) file transfer protocol. The AS4 tasks work with the existing GoAnywhere HTTP/S server as the message transport mechanism.
    • Added a new AS4 Resource for defining partner information, such as URLs, authentication, certificates, etc...
    • Added a new AS4 service, along with configuration pages for AS4 Message Channels.
    • Added a new AS4 Pull task for retrieving messages from an AS4 server.
    • Added a new AS4 Push task for sending messages to an AS4 server.
    • Added a new AS4 Send Error task for returning an error if validation of an AS4 message fails.
    • Added a new AS4 Send Receipt task for sending receipts in response to AS4 pull requests.
    • Added a new AS4 Enqueue Message task for adding messages to Web User Message Channels.
    • Added new Web user configuration options for AS4.
    • Added new AS4 server-side logs.

Fixes

  • Fixed an issue where MFT would fail to start up due to a missing security property. This issue was introduced in version 6.3.0.
  • Fixed a UI alignment issue in the SAN/DN section of Web User settings. This issue was introduced in version 6.3.0.
  • Fixed an issue where encryption GoFast file accelerated transfers would fail during key generation when running in FIPS mode using the new Bouncy Castle FIPS 140-2 certified security provider. This issue was introduced in 6.3.0.
  • Fixed an issue where encryption updates to the service keystore passwords were causing the Security Audit Report generation to fail. This issue was introduced in 6.3.0.
  • Fixed an issue where SOAP and REST tasks were not correctly handling implicit trust. This issue was introduced in version 6.3.0.
  • Fixed an issue where email and username validation was not properly enforced when performing SAN/DN verification during Web User authentication. This issue was introduced in 6.3.0.