Bob,
The certificates are a different issue, but it's possible they might need to be
replaced too.
This is why I upgraded our server. I don't use Authorize.net but do use PayPal
and they also require updated certificates and servers that use TLS 1.2 with
all other weaker protocols disabled.
I'm just using Apple's macOS Server, and the simplest way for me was to upgrade
to macOS Server 5.3 (or 5.3.1). Anything earlier than that still supported all
the vulnerable protocols, and not TLS 1.2.
Troy
I’ve gotten notices from Authorize.net <http://authorize.net/> about
their discontinuation of support for TLS 1.0 and 1.1; I have quite a few
web apps that I wrote and host that use Auth.net <http://auth.net/>, and
I’m just not clear on what I have to do.
From speaking with an Authorize.net <http://authorize.net/> tech, it
sounds like nothing has to change in the API that I used, but my guess
is that the web servers that host these sites MUST be running TLS 1.2.
Is this correct?
If that’s true, I’m assuming I’ll have to get new SSL certificates for
the sites that are using Auth.net <http://auth.net/>; is that correct?
Thanks for any insights,
Bob Patin
