You may have recently received an E-mail from Authorize.NET notifying you that early TLS will be disabled on September 18, 2017, and noting you should confirm your applications can use TLS 1.2 for API connections.
Do I need to take any action ?
If you are using SOLO Server Shared or Dedicated URL, no action is needed – our servers are compatible with this change.
If you are providing your own hosting for SOLO Server, action may be required depending on the version of SOLO Server you are currently running.
- You can determine what version of SOLO Server you are presently using by logging into the administration interface, scrolling down to the bottom of the home page, and looking for SOLO Server Build: X.X.X.X.
- If you are running SOLO Server version 1.16.1.2 or later, you should ensure that the system.webhttpRunTime element in your SOLO Server web.config file specifies the attribute targetFramework=”4.6.1“, and if not present, add the attribute.
- If you are running a SOLO Server Version between 1.13.3.4 and 1.16.1.2:
- You can upgrade SOLO Server.
- If you are not in a position to upgrade SOLO Server, you can apply the following workaround
- Install .NET 4.5 Framework or greater if not already installed on your server.
- In the registry, under HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft.NET/Framework/v4.0.30319, add a new DWORD entry named SchUseStrongCrypto with a value of 1. After making the change, reboot the server.
- If you are running a SOLO Server Version prior to 1.13.3.4, you will need to upgrade SOLO Server. Versions prior to 1.13.3.4 are targeted at the .NET Framework version 2.0, and no workaround is available for this version of the .NET Framework.
Please contact us with any questions.