<?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 SSL Certificate Updates for Legacy SDKs in News and Announcements</title>
    <link>https://community.developer.cybersource.com/t5/News-and-Announcements/SSL-Certificate-Updates-for-Legacy-SDKs/m-p/62935#M207</link>
    <description>&lt;P&gt;Beginning April 29, 2018, Authorize.Net began updating its SSL certificates on the &lt;A href="https://secure.authorize.net/gateway/transact.dll" target="_blank"&gt;secure.authorize.net&lt;/A&gt; and &lt;A href="https://developer.authorize.net/api/reference/index.html" target="_blank"&gt;api.authorize.net&lt;/A&gt; endpoints.&amp;nbsp; Legacy SDKs may point to these endpoints and therefore require a new &lt;A href="https://github.com/AuthorizeNet/sdk-php/blob/master/lib/ssl/cert.pem" target="_blank"&gt;cert.pem file located in Authorize.Net’s GitHub repository&lt;/A&gt;.&amp;nbsp; Additionally, if your payment solution pins Authorize.Net’s certificates or related information, please update accordingly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We greatly apologize for any inconvenience this may have caused.&lt;/P&gt;</description>
    <pubDate>Wed, 02 May 2018 23:10:47 GMT</pubDate>
    <dc:creator>RichardH</dc:creator>
    <dc:date>2018-05-02T23:10:47Z</dc:date>
    <item>
      <title>SSL Certificate Updates for Legacy SDKs</title>
      <link>https://community.developer.cybersource.com/t5/News-and-Announcements/SSL-Certificate-Updates-for-Legacy-SDKs/m-p/62935#M207</link>
      <description>&lt;P&gt;Beginning April 29, 2018, Authorize.Net began updating its SSL certificates on the &lt;A href="https://secure.authorize.net/gateway/transact.dll" target="_blank"&gt;secure.authorize.net&lt;/A&gt; and &lt;A href="https://developer.authorize.net/api/reference/index.html" target="_blank"&gt;api.authorize.net&lt;/A&gt; endpoints.&amp;nbsp; Legacy SDKs may point to these endpoints and therefore require a new &lt;A href="https://github.com/AuthorizeNet/sdk-php/blob/master/lib/ssl/cert.pem" target="_blank"&gt;cert.pem file located in Authorize.Net’s GitHub repository&lt;/A&gt;.&amp;nbsp; Additionally, if your payment solution pins Authorize.Net’s certificates or related information, please update accordingly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We greatly apologize for any inconvenience this may have caused.&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2018 23:10:47 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/News-and-Announcements/SSL-Certificate-Updates-for-Legacy-SDKs/m-p/62935#M207</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2018-05-02T23:10:47Z</dc:date>
    </item>
  </channel>
</rss>

