<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why the root cert for AIM transaction is not in https://curl.haxx.se/ca/cacert.pem ? in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Why-the-root-cert-for-AIM-transaction-is-not-in-https-curl-haxx/m-p/50018#M25525</link>
    <description>&lt;P&gt;I use CURL in PHP to connect with&amp;nbsp; &lt;A target="_blank" href="https://secure.authorize.net/gateway/transact.dll"&gt;https://secure.authorize.net/gateway/transact.dll&lt;/A&gt; . &amp;nbsp;Recently, few days ago, I got the CURL error message :&amp;nbsp;SSL certificate problem: unable to get local issuer certificate . This problem might have started after an update &amp;nbsp;of my CA bundle. &amp;nbsp;My&amp;nbsp;CA bundle is taken from&amp;nbsp; &lt;A target="_blank" href="http://curl.haxx.se/ca/cacert.pem"&gt;http://curl.haxx.se/ca/cacert.pem&lt;/A&gt; , I checked the required chain and neither the required root certificate or any of the intermediary certificates in the chain were available in the most recent version of that list. &amp;nbsp;I manually added the required root certificate in the file and the problem was solved. &amp;nbsp;However, I would have expexted that the required root certificate used by Authorize.net would have been sufficiently trusted to have been already included in this very standard list. Any explanation? &amp;nbsp;I also asked for explanation at Stack Overflow&amp;nbsp;&lt;A target="_blank" href="http://stackoverflow.com/questions/29103613/how-comes-authorize-net-uses-a-certificate-that-is-signed-with-a-ca-that-is-not"&gt;http://stackoverflow.com/questions/29103613/how-comes-authorize-net-uses-a-certificate-that-is-signed-with-a-ca-that-is-not&lt;/A&gt; , but no one seems to know the answer, &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Mar 2015 14:37:26 GMT</pubDate>
    <dc:creator>dominic108</dc:creator>
    <dc:date>2015-03-18T14:37:26Z</dc:date>
    <item>
      <title>Why the root cert for AIM transaction is not in https://curl.haxx.se/ca/cacert.pem ?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Why-the-root-cert-for-AIM-transaction-is-not-in-https-curl-haxx/m-p/50018#M25525</link>
      <description>&lt;P&gt;I use CURL in PHP to connect with&amp;nbsp; &lt;A target="_blank" href="https://secure.authorize.net/gateway/transact.dll"&gt;https://secure.authorize.net/gateway/transact.dll&lt;/A&gt; . &amp;nbsp;Recently, few days ago, I got the CURL error message :&amp;nbsp;SSL certificate problem: unable to get local issuer certificate . This problem might have started after an update &amp;nbsp;of my CA bundle. &amp;nbsp;My&amp;nbsp;CA bundle is taken from&amp;nbsp; &lt;A target="_blank" href="http://curl.haxx.se/ca/cacert.pem"&gt;http://curl.haxx.se/ca/cacert.pem&lt;/A&gt; , I checked the required chain and neither the required root certificate or any of the intermediary certificates in the chain were available in the most recent version of that list. &amp;nbsp;I manually added the required root certificate in the file and the problem was solved. &amp;nbsp;However, I would have expexted that the required root certificate used by Authorize.net would have been sufficiently trusted to have been already included in this very standard list. Any explanation? &amp;nbsp;I also asked for explanation at Stack Overflow&amp;nbsp;&lt;A target="_blank" href="http://stackoverflow.com/questions/29103613/how-comes-authorize-net-uses-a-certificate-that-is-signed-with-a-ca-that-is-not"&gt;http://stackoverflow.com/questions/29103613/how-comes-authorize-net-uses-a-certificate-that-is-signed-with-a-ca-that-is-not&lt;/A&gt; , but no one seems to know the answer, &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2015 14:37:26 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Why-the-root-cert-for-AIM-transaction-is-not-in-https-curl-haxx/m-p/50018#M25525</guid>
      <dc:creator>dominic108</dc:creator>
      <dc:date>2015-03-18T14:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why the root cert for AIM transaction is not in https://curl.haxx.se/ca/cacert.pem ?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Why-the-root-cert-for-AIM-transaction-is-not-in-https-curl-haxx/m-p/50071#M25573</link>
      <description>&lt;P&gt;See blog post regarding infrastructure and security upgrades:&amp;nbsp;&lt;A href="http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615" target="_blank"&gt;http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Mon, 23 Mar 2015 18:57:00 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Why-the-root-cert-for-AIM-transaction-is-not-in-https-curl-haxx/m-p/50071#M25573</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2015-03-23T18:57:00Z</dc:date>
    </item>
  </channel>
</rss>

