search

AuthorizeNet / sdk-php

PHP SDK for Authorize.Net API
Other
429 stars 403 forks source link

When will the cert.pem file be updated to reflect the Entrust to DigiCert SSL migration? #465

Open gellieann opened 1 week ago

gellieann commented 1 week ago

We are using this php sdk in our application, so we will be waiting for the updated file.

Thank you.

hikashop-nicolas commented 1 week ago

Same here. Please update the SDK with the new certificate.

demeritcowboy commented 6 days ago

I've submitted a pull request with the latest cert.pem available: https://github.com/AuthorizeNet/sdk-php/pull/466

One thing I don't understand from the update notice: https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-05545. It sounds like both the sandbox and production will switch at the same time, so how are you supposed to test it ahead of time? I checked and the sandbox still seems to have the Entrust cert (see below). But I can see that the new cert.pem has both the old entrust cert and new digicert cert.

> openssl s_client -connect apitest.authorize.net:443 -showcerts
CONNECTED(000001BC)
depth=2 C = US, O = "Entrust, Inc.", OU = See www.entrust.net/legal-terms, OU = "(c) 2009 Entrust, Inc. - for authorized use only", CN = Entrust Root Certification Authority - G2
verify return:1
depth=1 C = US, O = "Entrust, Inc.", OU = See www.entrust.net/legal-terms, OU = "(c) 2012 Entrust, Inc. - for authorized use only", CN = Entrust Certification Authority - L1K
verify return:1
depth=0 C = US, ST = California, L = Foster City, O = Authorize.Net, CN = *.authorize.net
verify return:1