Reply
Member
Posts: 3
Registered: ‎02-15-2018

TLS 1.2 Migration

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?

Posts: 492
Topics: 0
Kudos: 97
Blog Posts: 0
Ideas: 0
Solutions: 42
Registered: ‎04-28-2017

Re: TLS 1.2 Migration

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...

Powered by NexWebSites.com -
Certified Authorize.net developers
Member
Posts: 3
Registered: ‎02-15-2018

Re: TLS 1.2 Migration

This is a PC-based application, so I'm not sure what you mean by "server". Are there changes we need to make to each PC the application runs on?
Posts: 492
Topics: 0
Kudos: 97
Blog Posts: 0
Ideas: 0
Solutions: 42
Registered: ‎04-28-2017

Re: TLS 1.2 Migration

[ Edited ]

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. 

Powered by NexWebSites.com -
Certified Authorize.net developers
Member
Posts: 1
Registered: ‎03-02-2018

Re: TLS 1.2 Migration

[ Edited ]
Hi, we have a site that processes payments through Authorize.net making a post to the url https://secure.authorize.net/gateway/transact.dll, as of 03/01/2018, it is giving error when trying to process the payments, specifically the following error: "The request was aborted: Could not create SSL / TLS secure channel." I understand why I read that you have to configure the environment to start using TLS 1.2, which I did by applying the Microsoft fix that enables this functionality on the server and restarted it. The question is, is there any other modification that needs to be done to make it work again? Thank you so much.
Posts: 492
Topics: 0
Kudos: 97
Blog Posts: 0
Ideas: 0
Solutions: 42
Registered: ‎04-28-2017

Re: TLS 1.2 Migration

Lets see the code you are using.

Powered by NexWebSites.com -
Certified Authorize.net developers
Member
Posts: 3
Registered: ‎02-15-2018

Re: TLS 1.2 Migration

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.