We use authorize.net’s API via cfhttp. Authorize recently switched SSL providers as outlined in this article:
https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-05545
This occurred over the past few days. During that time, browser access to both their Sandbox and Production environments has switched back and forth between Entrust (old provider) and Digicert (new provider) and seems to have settled back to Entrust 
. The “List” option in the “SSL Certificates” section of the Lucee Admin has also alternated between both providers. Regardless of which certificate was indicated as active, cfhttp has been able to connect to both servers and return valid data. So, everything seems fine.
The article talks about “pinning” certificates, which is something I’ve never done, but I don’t know if it’s something Lucee does for me. Do I need to do something like this Where does Lucee get its default cacerts from? - #10 by Kai_Koenig but for DigiCert.com? Or is DigiCert already in the keystore? I remember having to do this ages ago, but I think that was for a relatively new SSL provider on a very old install of ACF. Digicert’s root cert is from 2013, and I don’t think Lucee’s even been around that long.
So, I guess my overall question is, is this a non-issue for this setup?
Thanks!