ShopSite Knowledgebase :: Authorize.net upgrading root certificate and switching to SHA-256 algorithm May 26th, 2015

Knowledgebase Home

Search the Knowledgebase

Browse by Category

Knowledgebase Home > General

Authorize.net upgrading root certificate and switching to SHA-256 algorithm May 26th, 2015

Product: ALL
Version: ALL
Platform: ALL

I have heard or been notified that on May 26th, 2015, Authorize.net will be upgrading various SSL certificates and switching to the SHA-256 encryption algorithm and that action may be required to make sure my application still works with these changes. Do these Authorize.net changes affect my ShopSite? Is there anything that I need to do?

We do not anticipate any ShopSite issues with these changes. ShopSite versions 12 sp1, 11 sp2, 10 sp2, 9.0, 8.3, and 7.1 (the most current point release for each ShopSite version since v7x) has been tested against the Authorize.net test server (which was scheduled to be updated with these changes back on March 31st, 2015) without any issue. We do not antipate these changes will have any effect on ShopSite's connection to the secure.authorize.net domain. Note that at this time ShopSite does NOT use the api.authorize.net domain.

Here is Authorize.net's announcement of the update for their sandbox (test) servers: http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615

Here is Authorize.net's announcement of the update for their production (live) servers: http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Production-Certificate-Upgrades-begin-May-26-2015/ba-p/50430

Note that according to the above post they are also updating/changing the IP address pools for their domains names. ShopSite uses a domain name to connect to Authorize.net, not a hardcoded IP address, so this change should not affect ShopSite merchants either, unless your host has firewall rules that limit outgoing connections to certain IP addresses. If you experience issues connecting to Authorize.net, ask your host to check their firewall rules to make sure connections to all secure.authorize.net IP addresses are allowed.

No related articles were found.