Upgrade to Tls 1.2 - Best approach ?

Hi there,

These days, a lot of payment gateways are starting to no longer accept connections using Tls 1.1, and are requiring connections over Tls 1.2.  

I was wondering, what is the recommended approach of implementing this in a plugin ?

I know from that from a .NET Web Application you can enforce this by:

1) Modifying the web.config (out of question for a plugin)
2) C# Code, liks this:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

I have searched in the source code for the official Authorize.NET plugin (https://github.com/nopSolutions/Authorize.Net-plugin-for-nopcommerce) , to see how did the team upgrade it to use Tls 1.2, but I was not able to find the line above.

So basically, my question is:

What does upgrading to Tls 1.2 mean, from a plugin's perspective ?


Regards,

Thanks a lot! You're right. I've created a work item. But we still have some time (details)

Hi, I just downloaded and tested the nopCommerce team Authorize.NET plugin for version 3.7 and the tls 1.2 code change was not included.  I modified it based on the github commit (https://github.com/nopSolutions/Authorize.Net-plugin-for-nopcommerce/commit/9aa458fe58fa956a2bedb2a10895ba15568d1e14#diff-04dd898c8d7e5b82d02e38ce85f9ee0c) and it worked in Authorize.NET's sandbox.
Was this change supposed to already be included in the official 2.01 plugin for version 3.7?

Thanks Stargate I had to use your code from github because the latest 3.7 plugin does not work. Hopefully this helps anyone with the following error: The request was aborted: Could not create SSL/TLS secure channel.

Interesting article about TLS and the .net framework version being used...
https://blogs.perficient.com/microsoft/2016/04/tsl-1-2-and-net-support/

Also this:
https://stackoverflow.com/questions/45382254/update-net-web-service-to-use-tls-1-2

I am using nop version 3.5, may I know where I can place below line of code
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
When I have tried to put this in global.ascx under
protected void Application_Start(){
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
}

still I face the problem, may I know how to resolve this TLS 1.2  related issue in Nop 3.5

"global.ascx"?

was it global.asax  
or  global.asax.cs and recompiled?

New York wrote:

It is global.asax.cs , typo mistake.

I have resolved this via below code

ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;

in Global.asax.cs on Application_Start() event and set targetFramework="4.6" in web.config and it start works.

Hello,
I just got a mail from PayPal telling they will require TLS 1.2 after June 30th.

I am using NopCommerce 3.9
And using the following Default Payment Gatways:

PayPal Standard Version: 1.35
Author: nopCommerce team

&

PayPal Direct Version: 2.14
Author: nopCommerce team

Im just wondering if it already supports TLS 1.2 or do i need to do something to make it support ?

Thanks,
Varun