stevepiercy / authorizenet_aim Goto Github PK

Around line 190 in the AuthorizeNet_AIM.inc file, what are these two "returns" for? After a bunch of back and forth testing, I finally found that to get the tag to work I had to comment them out. Were they just testing left overs?

// Send parameters to Authorize.Net. Cross fingers.
// return (#AIMParamArray);
#AIMResult = string(include_url(#AIMURL, -postparams=#AIMParamArray));
// return (#AIMResult);

...because LassoSoft has not updated Lasso 8.6 to use the latest libcurl.

See http://lasso.2283332.n4.nabble.com/Lasso-8-6-3-and-TLS-1-2-tt4644921.html and http://www.lassosoft.com/rhinotrac?id=8010

When using the options -tlsv12=TRUE and -curl=TRUE on macOS 10.12.6, an error is returned:

curl: (35) Unknown SSL protocol error in connection to test.authorize.net:-9836

The issue can be replicated by invoking curl directly via a terminal session, which confirms the issue is not with the AuthorizeNet_AIM tag, but with macOS's implementation of curl.

$ curl https://test.authorize.net/gateway/transact.dll --tlsv1.2
curl: (35) Unknown SSL protocol error in connection to test.authorize.net:-9836

macOS 10.12.6 has implemented curl built with OpenTransport which exhibits the behavior, and which in turn is called by the AuthorizeNet_AIM tag via shell and os_process.

The temporary workaround is to install curl via homebrew with brew install curl, then use its path to invoke curl in the AuthorizeNet_AIM tag.

Find:

        #AIMResult = string(shell('curl ' +#AIMURL + #curl_post_data + (#tlsv12 ? ' --tlsv1.2' | '')));

Replace:

        #AIMResult = string(shell('/usr/local/Cellar/curl/7.55.1/bin/curl ' +#AIMURL + #curl_post_data + (#tlsv12 ? ' --tlsv1.2' | '')));

See curl/curl#1703