API 1.6.0 Release ( Deprecation of Insecure TLS Protocols)

Question

MYOB is improving the security of the Exo API and will be disabling insecure versions of TLS of the Exo API and Relay. This means applications connecting to the API and Relay need to support TLS 1.2. Connections using TLS 1.0, 1.1 and 1.3 (until officially supported) will be rejected once the cutover is made.

To help facilitate a smooth cutover we are planning to deploy the new TLS configuration over the weekend of the 26th Nov so Partners and Developers can test and resolve any issues over the weekend. We will re-enable the existing configuration again on Monday 29th to ensure continuity of service for customers whose issues haven’t been resolved, however the hard cutover will be the weekend of the 4th of Dec.

We recommend that applications consuming the API are updated to the latest frameworks and auto negotiate the TLS protocol thereby futureproofing any changes in the future.

Release Links

API Installer

Release Notes

Will_H · Answer

: API 1.6.1 Released (Incremental improvements)

A new version of the API is available now.

This release contains fixes to API speed issue in OTG app & Extra field date issue in sales order while creating via OTG. Please refer to the release notes for more information.

API Installer

Release Notes

Will_H · Answer

Please Note:

The release notes/dependencies for the initial installer are incorrect.

Business Services 1.6 requires .NET Framework 4.7.2 OR 4.8 to run

The installer will allow it to install without error against 4.5+, but if you haven't got 4.7.2 or higher, the actual service will be unable to start.

Installers for .NET should always come from Microsoft, for ease of reference, the following link should work:

https://dotnet.microsoft.com/download/dotnet-framework/net472