You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.
Microsoft require TLS 1.2 to connect to OData endpoints in cloud applications such as Dynamics 365 SAT and Production environments. SSIS-Json-Source_Component runs under .NET Framework 4.0 which supports only TLS 1.0 by default.
As a short-term fix, it is possible to force TLS 1.2 in .NET 4.0 in Utils.cs by adding the following code just before the SendAsync request:
System.Net.ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
You do require .NET 4.5 to be installed alongside .NET 4.0 for this to work.
A better solution is to upgrade the projects to use .NET 4.5 or higher, which supports TLS 1.2 with an enumerated value:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
SSIS runtime on SQL Server 2016 and 2017 installs .NET 4.5 so this should work.
.NET 4.6 supports TLS 1.2 by default without any code changes, but .NET 4.6 libraries are not available to SSIS yet.
A good feature request would be for a configurable TLS version option in the GUI.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Microsoft require TLS 1.2 to connect to OData endpoints in cloud applications such as Dynamics 365 SAT and Production environments. SSIS-Json-Source_Component runs under .NET Framework 4.0 which supports only TLS 1.0 by default.
As a short-term fix, it is possible to force TLS 1.2 in .NET 4.0 in Utils.cs by adding the following code just before the SendAsync request:
System.Net.ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
You do require .NET 4.5 to be installed alongside .NET 4.0 for this to work.
A better solution is to upgrade the projects to use .NET 4.5 or higher, which supports TLS 1.2 with an enumerated value:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
SSIS runtime on SQL Server 2016 and 2017 installs .NET 4.5 so this should work.
.NET 4.6 supports TLS 1.2 by default without any code changes, but .NET 4.6 libraries are not available to SSIS yet.
A good feature request would be for a configurable TLS version option in the GUI.
The text was updated successfully, but these errors were encountered: