Enable TLS 1.2 on Cloud Connector host machine

As TLS 1.0 is no longer seen as secure, more and more vendors like Salesforce or Microsoft deprecate TLS 1.0 and recommend users to switch to more secure standards like TLS 1.2.

For users of the Layer2 Cloud Connector this means that existing connections can no longer run properly or could even stop running at all. To prevent your synchronizations from going stale we recommend configuring your host machine to enable TLS 1.2 and disable explicitly the deprecated version.

The .NET framework versions 4.5, 4.5.1 and 4.5.2 do not enable TLS 1.2 by default. As the Cloud Connector is built upon this .NET version, you have to enable TLS 1.2 AND disable 1.0 to force the framework using only TLS 1.2. Alternatively you can upgrade to the latest Layer2 Cloud Connector version, because as of V7.17.7.1 the .NET Framework has been updated to 4.6.2 which supports TLS 1.2. 

It is possible to enable TLS 1.2 by default without modifying any application by setting a specific value in the machine registry.

Please note that we recommend making registry changes only if you have proper experience in doing so. If you have no knowledge of editing the Windows registry, please ask your administrator or wait for an upcoming version of Cloud Connector that supports TLS 1.2 (with .NET 4.6) out of the box (no ETA available).

Update or create the SchUseStrongCrypto DWORD value in the following two registry keys to 1:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319

Although the version number in those registry keys is 4.0.30319, the .NET 4.5, 4.5.1, and 4.5.2 frameworks also use these values. Those registry keys, however, will enable TLS 1.2 by default in all installed .NET 4.0, 4.5, 4.5.1, and 4.5.2 applications on that system. It is thus advisable to test this change before deploying it to any of your production machines.

Please take into account that you have to reboot your machine after making the registry changes. 

ready to go next steps?