Authorize.Net Error: SSL Certificate Has Expired
Posted by Melodic_Tumbleweed33@reddit | linuxadmin | View on Reddit | 8 comments
Hi,
Hope I can get some help and this is the right place to ask. Please don't hurt me if not.
Basically running into an issue as titled. "Authorize.Net CIM Gateway Connection error: SSL certificate problem: certificate has expired" The SSL cert on the frontend is current and valid. The site sits behind Cloudflare which provides rolling active SSL cert.
On the backend I tried to update everything I could find: OpenSSL, curl, ca-bundle.crt, etc. The site is Magento 2 running on AWS Linux 2. The M2 extension that provides the Authnet solution is also updated. The extension itself also provides a cert as a fallback.
So, any ideas where this expired SSL certificate could be?
Friendly-Comedian-86@reddit
If it's Magento 2, the issue is likely that the underlying module is the ParadoxLabs CIM module, which includes a copy of the CA's root certificate. Since Auth.net changed certificate providers, that needs to be updated. Should be able to do so via:
Further details on this article:
https://www.cadence-labs.com/2024/10/magento-2-fix-authorize-net-error-ssl-certificate-has-expired/
Organic-Chance-8395@reddit
Thank you. Was having the same issue just all of the sudden.
This worked like a charm!
elisma@reddit
thanks!
xisonc@reddit
Authorize.net has a specific cert that gets loaded into CURL, its part of the Authorize.net SDK. See https://github.com/AuthorizeNet/sdk-php/tree/master/lib/ssl for an example.
outsellers@reddit
Is this working?
Melodic_Tumbleweed33@reddit (OP)
It doesn't match, but the fallback cert looks to be valid? https://github.com/ParadoxLabs-Inc/authnetcim/blob/master/authorizenet-cert.pem
xisonc@reddit
Yeah it looks like it was included in the authnetcim plugin version 5.1.1
Any idea what version of PHP you're using?
Melodic_Tumbleweed33@reddit (OP)
PHP 8.2.23. Openssl version says it's 1.1.1w. But it looks like the PHP is built with, and I'm not too familiar with this, OpenSSL 1.0.2k-fips. Could this be the issue?