TLS 1.0/1.1 sunset 

Our .NET integration toolkit does not automatically switch to TLS1.2 if it cannot communicate with TLS1.0 or TLS1.1. It needs to be forced to use TLS1.2 from the moment we stop supporting TLS1.0/1.1. 

This can be done in 2 ways:

1. Windows Registry settings on the environment that runs the toolkit
2. Add settings to the startup parameters of the toolkit

1. Windows registry settings

   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
   [HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\.NETFramework\\v4.0.30319]"SchUseStrongCrypto"=dword:00000001

2. Add settings to the startup parameters of the toolkit

In the App.config, for applications based on .NET Framework 4.0 or higher, the following parameter needs to be added:

    <runtime>
          <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false"/>    
    </runtime> 

For .NET Framework 3.5-based applications:

Add the following code snippet to the application initialisation: 

     System.Net.ServicePointManager.SecurityProtocol=(System.Net.SecurityProtocolType)3072;

There is also a nice blog by Kevin Chalet about Forcing an old .NET application to support TLS 1.2 without recompiling it.

Do you need help? Contact support or operations.