I have an existing C#.net application which uses the AuthorizeNet DLL to allow users to make credit card payments. What do I need to do to migrate to TLS 1.2? If I start using the newest DLL can I be sure my application will still work after February 28? If so, which version do I need? If not, what do I need to do?
02-15-2018 10:05 AM
If your application requires the use of the SDK, it should be using the newest version of the SDK.
Being able to make a TLS 1.2 connection is not only determined by your application, it is also dependent on your server environment and how it is configured. You can check your server's TLS 1.2 support by using one of the methods outlined at : https://community.developer.authorize.net/t5/Integration-and-Testing/TLS-1-2-Migration/m-p/61582/hig...
02-15-2018 12:47 PM
02-15-2018 01:15 PM
PC or server, the configuration for making an http request to Authorize.net would be the same. You may not need to make any modifications, test with the referenced code examples.
02-15-2018 01:21 PM - edited 02-15-2018 01:22 PM
Lets see the code you are using.
03-04-2018 04:51 AM
I had this problem, too. I searched the web site and found that others had the same problem. One solution was to add this code before sending the web request:
// This is necessary to avoid the message
// "The request was aborted: Could not create SSL/TLS secure channel."
const SslProtocols _TLS12 = (SslProtocols)0x00000C00;
const SecurityProtocolType TLS12 = (SecurityProtocolType)_TLS12;
ServicePointManager.SecurityProtocol = TLS12;
If you're using the sample code in the SDK, put this right at the top of the SendRequest method.
03-05-2018 09:05 AM