displaying top 100 results
Authorize.NET Temporarily Ending TLS 1.1 and TLS 1.0 Support
Tracker Comment Comment on CFHTTP/CFInvoke Fails with SSL Certificates using Subject Alternative Names (SAN) by External U.
2596846 CF-3566218 External U. Another SAN cert to test is https://sandbox.authorize.net/ (GET)
Authorize.net is switching to a SAN cert on 5/26/2015 and anyone still using ColdFusion 8 is going to be negatively impacted.
https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net
Portal Topic TLS 1.2 for ColdFusion 9 and Older
Wil Genovese TLS 1.2 for ColdFusion 9 and Older The upcoming Authorize.NET switch to using TLS 1.2 only has a lot of people scrambling to get their servers updated. This has been a long planned transition at Authorize.NET and at many/most/all other payment processing companies. The inevitable facts
Tracker Comment Comment on Extension to 3309220 . Change of behaviour from CF 9 when persisting UTC date/time by External U.
2613071 CF-3347145 External U. Just upgraded to CF10 on an eCommerce site and this bug breaks the Authorize.NET interface. Authorize.NET requires a UTC timestamp and their sample code returns local time instead.
Wil Genovese USPS Shipping API Ending TLS 1.1 and TLS 1.0 Support, is your ColdFusion Server Ready? At CF Webtools we recently went through a round of server upgrades to handle the Authorize.net ending support for older TLS versions. Now USPS, United State Postal Service, is doing the same thing
Tracker Issue Error after update 11
how many sites it affected. This one was particularly busy with processing transactions (this was the point of failure). One of the functions makes a call to authorize.net, so maybe that's related? The fix was to roll back update 11. I can't install update 11 until this is resolved or a fix