<?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 Need Help on Update Message ,Authorize.Net Direct Post from MD5 to SHA-512 in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68030#M41313</link>
    <description>&lt;P&gt;We have a ecommerece store on&amp;nbsp;&lt;SPAN&gt;Magento ver. 1.9.0.1 We are using Authorize CIM on our website , we got following notification as a critical update&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"&amp;nbsp;&lt;SPAN class="grid-row-title"&gt;Action required: Update Authorize.Net Direct Post from MD5 to SHA-512 – 3/1/2019&lt;/SPAN&gt;&lt;BR /&gt;Magento's implementation of the Authorize.Net Direct Post payment method uses MD5 based hash, and on March 14, 2019 Authorize.net will stop supporting MD5 based hash usage. This will result in Magento merchants not being able to process payments using Authorize.Net Direct Post. To avoid disruption and to continue processing payments, merchants need to apply a patch provided by Magento and add a Signature Key (SHA-512) in the Magento Admin configuration settings. For information on applying this patch please see the Magento Help Center. &lt;A href="https://support.magento.com/hc/en-us/articles/360024368392" target="_blank"&gt;https://support.magento.com/hc/en-us/articles/360024368392&lt;/A&gt; "&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please guide is this message linked to us ? Do we also need to update this patch on our site or its something different from what we are already using. ? As we have Authorize CIM on our store so is this patch necessary to be installed on our store ? I am confused please guide and help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 14 Jun 2019 15:25:35 GMT</pubDate>
    <dc:creator>adilkhan</dc:creator>
    <dc:date>2019-06-14T15:25:35Z</dc:date>
    <item>
      <title>Need Help on Update Message ,Authorize.Net Direct Post from MD5 to SHA-512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68030#M41313</link>
      <description>&lt;P&gt;We have a ecommerece store on&amp;nbsp;&lt;SPAN&gt;Magento ver. 1.9.0.1 We are using Authorize CIM on our website , we got following notification as a critical update&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"&amp;nbsp;&lt;SPAN class="grid-row-title"&gt;Action required: Update Authorize.Net Direct Post from MD5 to SHA-512 – 3/1/2019&lt;/SPAN&gt;&lt;BR /&gt;Magento's implementation of the Authorize.Net Direct Post payment method uses MD5 based hash, and on March 14, 2019 Authorize.net will stop supporting MD5 based hash usage. This will result in Magento merchants not being able to process payments using Authorize.Net Direct Post. To avoid disruption and to continue processing payments, merchants need to apply a patch provided by Magento and add a Signature Key (SHA-512) in the Magento Admin configuration settings. For information on applying this patch please see the Magento Help Center. &lt;A href="https://support.magento.com/hc/en-us/articles/360024368392" target="_blank"&gt;https://support.magento.com/hc/en-us/articles/360024368392&lt;/A&gt; "&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please guide is this message linked to us ? Do we also need to update this patch on our site or its something different from what we are already using. ? As we have Authorize CIM on our store so is this patch necessary to be installed on our store ? I am confused please guide and help&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jun 2019 15:25:35 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68030#M41313</guid>
      <dc:creator>adilkhan</dc:creator>
      <dc:date>2019-06-14T15:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: Need Help on Update Message ,Authorize.Net Direct Post from MD5 to SHA-512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68039#M41319</link>
      <description>&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/31004"&gt;@adilkhan&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;Do you use direct post method to process payments? The above refers to DPM.</description>
      <pubDate>Sun, 16 Jun 2019 19:18:54 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68039#M41319</guid>
      <dc:creator>Renaissance</dc:creator>
      <dc:date>2019-06-16T19:18:54Z</dc:date>
    </item>
    <item>
      <title>Re: Need Help on Update Message ,Authorize.Net Direct Post from MD5 to SHA-512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68044#M41322</link>
      <description>&lt;P&gt;We are using Authorize CIM method on our website. Do we have to update this patch then on our website ?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2019 11:47:47 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Help-on-Update-Message-Authorize-Net-Direct-Post-from-MD5/m-p/68044#M41322</guid>
      <dc:creator>adilkhan</dc:creator>
      <dc:date>2019-06-17T11:47:47Z</dc:date>
    </item>
  </channel>
</rss>

