Jump to content

Question

3 answers to this question

Recommended Posts

  • 0
Posted

So yes, Authorize.net now requires your server communicate over TLS 1.2. They have dropped support for TLS 1.0 and 1.1. If you haven't already, contact your hosting provider and tell them that you need support for TLS 1.2 and they should either add support for that or move your account over to a server that does.

  • 0
Posted
On 3/21/2018 at 8:56 PM, riverwatcher said:

So next question is how to update to support TLS 1.2. 

This depends on your server software and OS. I am most familiar with CentOS, and I know that CentOS 5 does not support TLS 1.2. Support was added for TLS 1.2 for curl/PHP in version 6.8 or 6.9 I believe, but CentOS 7.4 is recommended. So you may need to upgrade or deploy a more modern OS. Your hosting provider is probably the best place to contact for additional help and details.

Blesta itself will work over TLS 1.2, and the Authorize.net gateway is compatible.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...