ColdFusion CFHTTP AIM Akamai update was working... then stopped

alambert-wf — Wed, 22 Jun 2016 18:05:04 GMT

My environment is running ColdFusion 10 on Windows Server 2012.

We have a few applications using the Authorize.NET AIM method via the CFHTTP tag.

I've simplified the code, but roughly this is the execution...

<cfset postToThisURL = "https://secure.authorize.net/gateway/transact.dll">
<cfset testTrans = "FALSE">

<cfhttp method="Post" url="#postToThisURL#">
   <cfhttpparam type="Formfield" name="x_login" value="#authLoginID#">
   <cfhttpparam type="Formfield" name="x_tran_key" value="#hashingKey#">

   <cfhttpparam type="Formfield" name="x_version" value="3.1">
   <cfhttpparam type="Formfield" name="x_type" value="AUTH_CAPTURE">
   <cfhttpparam type="Formfield" name="x_method" value="CC">
   <cfhttpparam type="Formfield" name="x_recurring_billing" value="FALSE">
   <cfhttpparam type="Formfield" name="x_amount" value="#chargeTotal#">
   <cfhttpparam type="Formfield" name="x_test_request" value="#testTrans#">
   <cfhttpparam type="Formfield" name="x_duplicate_window" value="0">
   <cfhttpparam type="Formfield" name="x_invoice_num" value="#left(invoiceNumber,20)#">
   <cfhttpparam type="Formfield" name="x_description" value="#descriptionTxt# - #dateFormat(now(),'mm/dd/yyyy')#">

   <cfhttpparam type="Formfield" name="x_customer_ip" value="#userIP#">
   <cfhttpparam type="Formfield" name="x_delim_data" value="TRUE">
   <cfhttpparam type="Formfield" name="x_delim_char" value="|">
   <cfhttpparam type="Formfield" name="x_encap_char" value="">
   <cfhttpparam type="Formfield" name="x_relay_response" value="FALSE">

   <cfhttpparam type="Formfield" name="x_first_name" value="#left(listFirst(tempBuyer.ccName,' '),50)#">
   <cfhttpparam type="Formfield" name="x_last_name" value="#left(listRest(tempBuyer.ccName,' '),50)#">
   <cfhttpparam type="Formfield" name="x_address" value="#tempBuyer.ccAddress#">
   <cfhttpparam type="Formfield" name="x_city" value="#tempBuyer.ccCity#">
   <cfhttpparam type="Formfield" name="x_state" value="#tempBuyer.ccState#">
   <cfhttpparam type="Formfield" name="x_zip" value="#tempBuyer.ccZip#">
   <cfhttpparam type="Formfield" name="x_phone" value="#tempBuyer.ccPhone#">
   <cfhttpparam type="Formfield" name="x_email" value="#tempBuyer.ccEmail#">

   <cfhttpparam type="Formfield" name="x_card_num" value="#tempCardInfo.ccNumber#">
   <cfhttpparam type="Formfield" name="x_exp_date" value="#tempCardInfo.ccExpireMo##tempCardInfo.ccExpireYr#">
   <cfhttpparam type="Formfield" name="x_card_code" value="#tempCardInfo.ccSecurity#">

</cfhttp>

A while back, we changed the post location from:

https://secure.authorize.net/gateway/transact.dll

https://secure2.authorize.net/gateway/transact.dll

This was largely based on the updated AIM documentation (page 33)

http://www.authorize.net/content/dam/authorize/documents/AIM_guide.pdf

With this change, we had some issues in testing.

The thing that got us over those issues was this post:

https://community.developer.authorize.net/t5/Integration-and-Testing/Production-Certificate-Upgrades-begin-May-26-2015/m-p/50882#M26291

With this information, I proceeded to bind the certificates to our CF environment.

------------

All of our clients transactions were processing correctly via the code above, using the "secure2" path.

But sometime between June 12th and June 15th, we started getting the following message in the response:

Error Detail: Connect Exception: Connect to secure2.authorize.net:443 [secure2.authorize.net/23.218.121.147] failed: Connection timed out: connect

File Content: Connection Failure

Statuscode: Connection Failure. Status code unavailable.

Mimetype: Unable to determine MIME type of file.

I have yet to determine the cause.

We have been forced to set all of our applications back to the old path for the time being.

---------------

I don't have a lot of ideas, so I was hoping to reach out and see if anyone has had similar issues and knows a solution. If I'm lacking any details, ask and I'll try to gather the information.

---------

Also, is it possible that the method I'm using is no longer valid?

I'm asking because the upgrade guide mentions that AIM is now "Payment Transactions".

http://developer.authorize.net/api/upgrade_guide/

and an example here is using XML instead of Form Fields over CFHTTP:

http://stackoverflow.com/questions/37196150/authorize-net-what-variable-name-should-i-use-when-posting-xml-data-via-coldf

Thanks in advance,

Adam

Re: ColdFusion CFHTTP AIM Akamai update was working... then stopped

Joy — Tue, 28 Jun 2016 19:10:28 GMT

Hi Adam,

To address your questions:

We can confirm that your connection method is valid. AIM is no longer the preferred method and is not receiving feature updates, but is fully supported.
We can confirm that we haven't updated the certificates on our Akamai endpoints.
Unfortunately, we don't know what the problem is for you, but note that the Akamai upgrade is no longer absolutely required as announced here: https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/IMPORTANT-June-30th-Akamai-SureRoute-Now-Voluntary/ba-p/54914

Thanks,

Joy

topic Re: ColdFusion CFHTTP AIM Akamai update was working... then stopped in Integration and Testing

ColdFusion CFHTTP AIM Akamai update was working... then stopped

Re: ColdFusion CFHTTP AIM Akamai update was working... then stopped