Reply
Member
Posts: 5
Registered: ‎10-15-2013

TLS 1.2 Issue - in Classic ASP environment

I manage a few sites that still use Classic ASP.

The method of connection is via a MSXML2 component pointing to https://secure.authorize.net/gateway/transact.dll

Is there a simple change i can make in this code somewhere (see below), to test via the sandbox, and see if the server is TLS 1.2 compliant?

 

Thanks!

 

[code]

set objHttp = server.Createobject("MSXML2.ServerXMLHTTP")
if err.number <> 0 then
    Response.write(err.Description)
    response.End()
end if
'on error goto 0

objHttp.open "POST", strPost, false
objHttp.Send strRequest

'Get response
objHttpStatus = objHttp.status
strResponse   = objHttp.responseText
set objHttp      = nothing

[/code]

Posts: 2,251
Topics: 51
Kudos: 151
Blog Posts: 64
Registered: ‎12-05-2011

Re: TLS 1.2 Issue - in Classic ASP environment

Hello @snooper

 

Another developer asked a similar question on StackOverflow and there are several suggestions to help: http://stackoverflow.com/questions/34997849/classic-asp-outbound-tls-1-2

 

Richard

--------

Webhooks are now available for Authorize.Net

Using SOAP, see our deprecation notice.
Check out Accept.js, our Javascript replacement for DPM.
Pro Tip: Never use test mode in the sandbox, instead use the Testing Guide.
Posts: 63
Topics: 0
Kudos: 4
Blog Posts: 0
Ideas: 0
Solutions: 3
Registered: ‎04-28-2017

Re: TLS 1.2 Issue - in Classic ASP environment

[ Edited ]

You may not need to modify your code at all, but you may need to apply the update from : 

 https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1.1-and-tls-1.2-as-a-default-..., there is also an Easy Fix on the same page that will modify your registry entries for you.

Powered by NexWebSites.com -
Certified Authorize.net developers
Member
Posts: 5
Registered: ‎10-15-2013

Re: TLS 1.2 Issue - in Classic ASP environment

@RichardH- thanks for the reponse.

You will actually see a comment of mine (kneidels) from back in November :-)

 

@NexusSoftware- thanks also.

 

Just to clarify - my setup currently works (for now...)i just want to be able to TEST with the tls1.2 version with the sandbox, while leavinjg the current setup active (meaning, probably not changing registry values etc)

 

is there a way to do this, in your opinion?

 

Thanks

Posts: 63
Topics: 0
Kudos: 4
Blog Posts: 0
Ideas: 0
Solutions: 3
Registered: ‎04-28-2017

Re: TLS 1.2 Issue - in Classic ASP environment

What version of Windows and the .Net framework is on your server?

 

Below is a simple test script that will return what your Schannel.dll is connecting with:

<%
Set objHttp = Server.CreateObject("MSXML2.ServerXMLHTTP.6.0")
objHttp.open "GET", "https://howsmyssl.com/a/check", False
objHttp.Send
Response.Write objHttp.responseText 
Set objHttp = Nothing 
%>

Save as testssl.asp and hit it with your browser.  If it returns the with tls_version":"TLS 1.2, you are good to go. 

Powered by NexWebSites.com -
Certified Authorize.net developers
Highlighted
New Member
Posts: 2
Registered: ‎05-17-2017

Re: TLS 1.2 Issue - in Classic ASP environment

For us, the magic was changing all of the objects of type ("MSXML2.ServerXMLHTTP" or "MSXML2.ServerXMLHTTP.3.0") over to the newer "MSXML2.ServerXMLHTTP.6.0".

 

It would make intuitive sense that the one without the version number chooses the newest version, but this is NOT the case, as it in fact points to the older 3.0 version.