Forcing Payment Gateway to Use TLS 1.2
Posted: Sun Apr 03, 2016 7:16 pm
Hi there,
We're using PayPal Payflow as our payment gateway.
PayPal's new requirements are that we have to use TLS 1.2 for all connections to them.
This will involve the following:
1. Moving the installation to a server running an OS that supports TLS 1.2 (e.g. Windows 2008 R2).
2. Moving AC 7 to use ASP.NET 4.x. Right now, it's running on 2/3.5.
3. Disabling all versions of SSL and TLS earlier than 1.2.
Does this seem like a reasonable plan? Is there anything missing here?
Also, what would be involved in moving AC 7 to ASP.NET 4.x? Is there a guide somewhere online?
Thanks,
Moustafa
We're using PayPal Payflow as our payment gateway.
PayPal's new requirements are that we have to use TLS 1.2 for all connections to them.
This will involve the following:
1. Moving the installation to a server running an OS that supports TLS 1.2 (e.g. Windows 2008 R2).
2. Moving AC 7 to use ASP.NET 4.x. Right now, it's running on 2/3.5.
3. Disabling all versions of SSL and TLS earlier than 1.2.
Does this seem like a reasonable plan? Is there anything missing here?
Also, what would be involved in moving AC 7 to ASP.NET 4.x? Is there a guide somewhere online?
Thanks,
Moustafa