TLS 1.2 in Eway payment gateway

Hi

I just received an email from Eway payment gateway provider as follows;

From August 2017, we will be rolling out changes to the TLS (Transport Layer Security) infrastructure across the eWAY payment system and MYeWAY portal. These changes will impact all browsers or systems that use TLS 1.0 or TLS 1.1. Any connection attempts made that are not using TLS 1.2 protocols will be rejected and you will not be able to access eWAY or our payment system.

This change may require you to update your website or platform code to ensure your own systems use the TLS 1.2 protocol. If your systems are not using TLS 1.2 after we have disabled older versions of the protocol, your payments will not be processed and you will not be able to access the payment system.


I am using eway payment gateway in nopCommerce 3.70. The payment plugin is the one from your website, plugin developed by nopCommerce team, Version: 1.03

So what does that message mean for me?  Do I need to make any code changes on my side?

Hi,

I think can modify 3.7  \Nop.Web\Global.asax.cs

Add the following code

    protected void Application_Start()
        {
            //most of API providers require TLS 1.2 nowadays
            ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

......}

I will just add that this CAN also be done (Thanks Alex @ Foxnetsoft!) without modifying the source by just adding that same bit of code into your Global.asax and initiate it using a runat server script which fires on application start, like this:

<%@ Application Codebehind="Global.asax.cs" Inherits="Nop.Web.MvcApplication" Language="C#" %>
<script runat="server">
    void Application_Start(object sender, EventArgs e)
    {
        // Code that runs on application startup
  System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
    }
</script>

You'll either have to reboot your server or restart the application in IIS before it takes effect.

ALSO, and more importantly....you can also just upgrade to >> 3.80 >> 3.90 and the problem is solved.