authorize.net AIM update needed?

[evolvewh]

I just received this email from Authorize.net today and it appears an update needs to be made but I'm not a skilled enough coder:

 

Dear Authorize.Net Merchant:

As you may be aware, new PCI DSS requirements state that all payment systems must disable earlier versions of TLS protocols. These older protocols, TLS 1.0 and TLS 1.1, are highly vulnerable to security breaches and will be disabled by Authorize.Net on February 28, 2018.

 

To help you identify if you’re using one of the older TLS protocols, Authorize.Net will temporarily disable those connections for a few hours on January 30, 2018 and then again on February 8, 2018. 

 

Please refer to our TLS FAQs for important details.

 

Based on the API connection you are using, on either one of these two days you will not be able to process transactions for a short period of time. If you don’t know which API you’re using, your solution provider or development partner might be a good resource to help identify it. This disablement will occur on one of the following dates and time:

 

• Akamai-enabled API connections will occur on January 30, 2018 between 9:00 AM and 1:00 PM Pacific time.
• All other API connections will occur on February 8, 2018 between 11:00 AM and 1:00 PM Pacific time.

Merchants using TLS 1.2 by these dates will not be affected by the temporary disablement. We strongly recommend that connections still using TLS 1.0 or TLS 1.1 be updated as soon as possible to the stronger TLS 1.2 protocol. If your current Virtual Point of Sale (VPOS) is an Authorize.Net product, please call Authorize.Net Customer Support at 1.877.447.3938 for assistance in updating to TLS 1.2.

 

Note: If you are not using a current version of a web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by visiting https://www.howsmyssl.com/. 

 

If you have any questions about this email or the upcoming TLS disablement, please refer to our TLS FAQs. Thank you for your attention to this matter and for being an Authorize.Net merchant.

Is anyone else receiving this email?

[Tyson]

This affects the server Blesta is installed on. The server must support TLS v1.2 in order for Blesta to communicate with Authorize.net since they are disabling support for TLS v1.0 and v1.1. You should contact your web host to ensure TLS v1.2 is supported.

[Paul]

Just to add.. CentOS 5 does not support TLS 1.2 via CURL. You must be running CentOS 6.9 or CentOS 7.x (Unless you're running a totally different flavor of Linux in which case I have no idea)

[evolvewh]

Thanks for the info Tyson and Paul and I think we're all set now.