<?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 Re: ColdFusion AIM integration: upgrading from MD5 to SHA512 in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66655#M40171</link>
    <description>&lt;P&gt;thanks Richard that helped. I was making incorrect assumptions&lt;/P&gt;</description>
    <pubDate>Fri, 01 Mar 2019 05:00:04 GMT</pubDate>
    <dc:creator>MThomas</dc:creator>
    <dc:date>2019-03-01T05:00:04Z</dc:date>
    <item>
      <title>ColdFusion AIM integration: upgrading from MD5 to SHA512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66626#M40144</link>
      <description>&lt;P&gt;Have an existing, working AIM integration program written in ColdFusion, but currently uses MD5 hash. Am having a hard time finding much in the way of sample ColdFusion code on the site to help in the migration to the SHA512 hash.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've gone in the Sandbox and generated a Signature Key. Do I use that in any of the x_* fields I send TO authorize.net? I thought that it was to go in the x_trans_key field instead of the old Transaction Key. If I test using the original transaction Key in x_trans_key it works. If I do nothing more than put the new Signature Key into the x_trans_key field it says invalid login or password or transaction. I'm not getting any farther than that so not even to the part where I string together the Signature Key field and other 2 and convert it to the new hash.&amp;nbsp; Is the Signature Key ONLY for converting to the hash (with the other 2 fields) once I get the api response back and not needed anywhere in the data sent to them?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 10:22:43 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66626#M40144</guid>
      <dc:creator>MThomas</dc:creator>
      <dc:date>2019-02-28T10:22:43Z</dc:date>
    </item>
    <item>
      <title>Re: ColdFusion AIM integration: upgrading from MD5 to SHA512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66629#M40147</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/28831"&gt;@MThomas&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;...&amp;nbsp; Is the Signature Key ONLY for converting to the hash (with the other 2 fields) once I get the api response back and not needed anywhere in the data sent to them?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Correct.&amp;nbsp; The signature key is ONLY used to validate the transaction RESPONSE is authentic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 13:34:16 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66629#M40147</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2019-02-28T13:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: ColdFusion AIM integration: upgrading from MD5 to SHA512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66642#M40159</link>
      <description>&lt;P&gt;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/28831"&gt;@MThomas&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;here's what worked for me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;cfset authNetBinarySignatureKey = binaryDecode(x_secret_key, "hex") /&amp;gt;&lt;BR /&gt;&amp;lt;cfset x_fp_hash=HMAC("#x_login#^#x_fp_sequence#^#x_fp_timestamp#^#x_amount#^#x_currency_code#","#authNetBinarySignatureKey#","HMACSHA512")&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;good luck!&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 21:31:43 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66642#M40159</guid>
      <dc:creator>MinneSnowtain</dc:creator>
      <dc:date>2019-02-28T21:31:43Z</dc:date>
    </item>
    <item>
      <title>Re: ColdFusion AIM integration: upgrading from MD5 to SHA512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66643#M40160</link>
      <description>&lt;P&gt;I think AIM (per the update page) uses the same 3 fields as the newest API. AuthName, TransID, and Amount.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 22:20:31 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66643#M40160</guid>
      <dc:creator>kabutotx</dc:creator>
      <dc:date>2019-02-28T22:20:31Z</dc:date>
    </item>
    <item>
      <title>Re: ColdFusion AIM integration: upgrading from MD5 to SHA512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66655#M40171</link>
      <description>&lt;P&gt;thanks Richard that helped. I was making incorrect assumptions&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 05:00:04 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66655#M40171</guid>
      <dc:creator>MThomas</dc:creator>
      <dc:date>2019-03-01T05:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: ColdFusion AIM integration: upgrading from MD5 to SHA512</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66656#M40172</link>
      <description>&lt;P&gt;thanks for the sample coldFusion code. I'm using AIM method with value pairs so it wasn't exactly what I needed to do, but it got me on the right path and saved me digging up the functions to convert to binary, and hash. Very helpful. thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is what ended up working for me in case it helps someone else doing the same AIM methods we use:&lt;/P&gt;&lt;P&gt;&amp;lt;cfset v_msg = "^" &amp;amp; loginid &amp;amp; "^" &amp;amp; v_transID &amp;amp; "^" &amp;amp; v_returned_amt &amp;amp; "^"&amp;gt;&lt;BR /&gt;&amp;lt;cfset sigk_binary = binaryDecode(v_sigk, "hex") /&amp;gt;&lt;BR /&gt;&amp;lt;cfset x_fp_hash = HMAC("#v_msg#","#sigk_binary#","HMACSHA512")&amp;gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 05:03:14 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/ColdFusion-AIM-integration-upgrading-from-MD5-to-SHA512/m-p/66656#M40172</guid>
      <dc:creator>MThomas</dc:creator>
      <dc:date>2019-03-01T05:03:14Z</dc:date>
    </item>
  </channel>
</rss>

