I have been asked to update four NOPCommerce sites using version 3.6 to work with the upcoming TLS 1.2 changes at Authorize.net. They all use the standard NOP plugin and one is a multistore using two copies of the plugin to connect to different Authorize.Net accounts.
I have seen threads here suggesting the fix below:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
Adding the above the Global.asx and recompiling, then deploying the Nop.Web.dll file.
Will this work in version 3.6?
Is there any other required work?
Is there a better way, or is one coming in the near future?
I do have IISCrypto avaikable if that helps. I know the server supports TLS 1.2 also (Server 2012).