Community Feedback

So what do you think about this community of ours? Or Authorize.Net in general? Suggestions for improvement, as well as kudos on what you do like, are always welcome.

Reply
Member
Posts: 3
Registered: ‎01-29-2018

TLS disablement ,Will solutions developed on .net framework 4.0 work on TLS 1.2.?

 We are using authorize.net payment gateway API from last 6 years.We have receieved the TLS disablement notice. We have few questions.Please see below.

 

 

 

  We are using CIM (Customer information Manager) soap calls for storing card information and payment transactions  .

 

Currently we are using  https://api.authorize.net/soap/v1/Service.asmx  url for Live transactions.

 

and https://apitest.authorize.net/soap/v1/Service.asmx  for test transcations .

 

We have developed our solution on .Net Framework 4.0 .

 

 Here are my queries ....

 

  1. Will the CIM soap calls get deprecated after 28th feb , if yes then what api's shoud we use ? 
  2.   Are the new APis supported in .Net Framework 4.0? If not what is the minimum .Net framework version required?

3.  We have hosted our web-portal on windows server 2016 ? will this support TLS 1.2 ?

 

Highlighted
Authorize.Net Expert
Posts: 121
Registered: ‎03-28-2014

Re: TLS disablement ,Will solutions developed on .net framework 4.0 work on TLS 1.2.?

Hi there,

 

CIM SOAP (or any SOAP methods) will not be shut off in February (they're independent of the TLS disablement) however SOAP is a deprecated API meaning that we do not add new features there and it will be End-Of-Lifed at some point in the future.  See https://developer.authorize.net/api/upgrade_guide/ for more details.

 

We recommend moving to the XML/JSON Anet API (https://developer.authorize.net/api/reference/index.html ) it should be pretty easy moving from SOAP, you can also avail of our .NET SDK https://github.com/AuthorizeNet/sdk-dotnet which supports .NET 3.5 and later.

 

Finally, on your portal, you can check if it supports TLS1.2 by testing it against our sandbox which is only supporting TLS1.2

 

Hope this helps,

 

Brian

Member
Posts: 3
Registered: ‎01-29-2018

Re: TLS disablement ,Will solutions developed on .net framework 4.0 work on TLS 1.2.?

Thanks for your reply,

 

  I have started using authorize.net 1.94 api directly in my application by adding the reference. i have made the test app which is working fine. Will this test api calls mad by my api already using TLS 1.2. Please confirm.thanks again

Member
Posts: 8
Registered: ‎06-03-2018

Re: TLS disablement ,Will solutions developed on .net framework 4.0 work on TLS 1.2.?

hello,

is this about the connection error issue?

NET 4.6 and above. You don’t need to do any additional work to support TLS 1.2, it’s supported by default.
.NET 4.5. TLS 1.2 is supported, but it’s not a default protocol. You need to opt-in to use it. The following code will make TLS 1.2 default, make sure to execute it before making a connection to secured resource:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
.NET 4.0. TLS 1.2 is not supported, but if you have .NET 4.5 (or above) installed on the system then you still can opt in for TLS 1.2 even if your application framework doesn’t support it. The only problem is that SecurityProtocolType in .NET 4.0 doesn’t have an entry for TLS1.2, so we’d have to use a numerical representation of this enum value:
ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
.NET 3.5 or below. TLS 1.2 is not supported (*) and there is no workaround. Upgrade your application to more recent version of the framework.

best regards  Download Bluestacks Download TextNow Download Photomath

craig