Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
If the SDK relies on the framework we are using, can I ask why a new release of the SDK was required?
Is it just that the .NET version of the MYOB.AccountRight.SDK.dll been changed?
Can you advise what version of .NET the MYOB.AccountRight.SDK.dll and AccountRight itself now target?
If we can keep in step it should reduce support issues.
Also, I couldn't find any documentation explaining what has changed in this release of the SDK. It has been a couple of years since the last version. Have any new endpoints been added?
Yes. I understand that now. https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls
@MYOBApi on Twitter mentions "the SDK relies on the underlying .NET framework you have used. If it's updated to support TLS1.1 or TLS1.2 the SDK will work fine. Only 4 of the 53,282 were using TLS1.0 & all have been communicated to" I am actually still worried. Surely the SDK relies on the underlying .Net framework that the SDK is using?. I was relieved to see the upgraded SDK on Nuget yesterday.
September 2018 - last edited September 2018
I installed https://www.nuget.org/packages/MYOB.AccountRight.API.SDK/2018.1.141-rc1 and made all my projects use Framework 4.6.1 now Wireshark has none of the TLSv1 packets
I see that 2016.2.99 has 54,282 downloads whilst the latest release candidate has 35 downloads!
I installed wireshark ( I am on a steep learning curve here)
I can see some packets with TLSv1.2 and some with TLSv1 any tips on how to tell if the packet is going to/coming from the API ?
I believe you should be able to use WireShark to explore the calls your code is making
There is an interesting StackOverflow here https://stackoverflow.com/questions/34276358/how-to-test-which-version-of-tls-my-net-client-is-using that references http://www.moserware.com/2009/06/first-few-milliseconds-of-https.html and https://albertx.mx/https-handshake/ as examples of this
Is there any way I can test whether my program will work as it is, or even work with the new sdk without just waiting till Sept 30?
Right I've had a quick chat with the engineering team.
You are right, the SDK does say it uses .Net4.5
.Net4.5 is (or can be) TLS1.1 and TLS1.2 compliant
Good news, the engineering team are right now testing an SDK update to help with this.
It's in Release Candidate now - which you are welcome to check out here https://www.nuget.org/packages/MYOB.AccountRight.API.SDK/2018.1.141-rc1
And all going well, they intend to release the production update for the SDK in the coming days
I am thinking that the Framework version for the MYOB.AccountRight.SDK.dll released by Nuget will determine the TLS support. looking at the dll in notepad I see it is framework 4.5
From https://stackoverflow.com/questions/28286086/default-securityprotocol-in-net-4-5 I gather that to support this, I would need to edit the registry.
It seems odd to me that the MYOB.AccountRight.SDK.Dll is not currently available on Nuget with the correct version. Is it just me or are there other developers fast developing a panic ? Or is there still something I don't understand perhaps?