Have an older website that cant be upgraded due to older third party custom controls. The server was configured approximately a year ago to use TLS1.2 and all older versions where disabled.
This is the soap call being used to initiate the connection. It initiates acall and immediately closes.
[System.Web.Services.Protocols.SoapDocumentMethodAttribute("https://api.authorize.net/soap/v1/ARBCancelSubscription", RequestNamespace="https://api.authorize.net/soap/v1/", ResponseNamespace="https://api.authorize.net/soap/v1/", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
public ARBCancelSubscriptionResponseType ARBCancelSubscription(MerchantAuthenticationType merchantAuthentication, long subscriptionId) {
object[] results = this.Invoke("ARBCancelSubscription", new object[] {
merchantAuthentication,
subscriptionId});
return ((ARBCancelSubscriptionResponseType)(results[0]));
}
โ03-05-2018 06:39 AM
Remove your dependency on 3rd party controls. The application is very likely to be using deprecated endpoints and methods.
โ03-05-2018 08:39 AM
Third party controls make up 60 percent of the site. It would be easier to switch merchants
โ03-05-2018 08:53 AM
You should check with the following, to ensure your server actually was configured properly:
using System; using System.Net; using System.IO; namespace howsMySSL { public partial class Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls; var response = WebRequest.Create("https://www.howsmyssl.com/a/check").GetResponse(); var responseData = new StreamReader(response.GetResponseStream()).ReadToEnd(); Response.Write(responseData); } } }
โ03-05-2018 09:05 AM