cancel
Showing results for 
Search instead for 
Did you mean: 

DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

The transactions and posting back to our server has been working.

We disabled TLS 1.0 on the server and only allow TLS 1.1 or TLS 1.2

 

This broke the post back and get the following

"An error occurred while trying to report this transaction to the merchant" on https://secure.authorize.net/gateway/transact.dll

 

The transaction is taken/recorded by Authorize.net. It just fails to post back/load the x_relay_url

 

The x_relay_url, page it should post back to, is on port 443(https)

It is a .net webforms page that has a javascript redirect on it.

 

Any ideas why this change would break the post back?

 

Environment:

Windows Server 2008, IIS 7.5

 

 

vincet
Contributor
22 REPLIES 22

Hello everyone,

 

Your report was escalated today to operations.  Stay tuned for further updates.

 

Richard

@RichardH, Thanks for the update!

Hi @RichardH

 

Any updates on this?

 

Our client's current validation status with American Express DSOP will expire on
7/1 and we are hoping to close this issue by then.

 

Thank you.

Hello @vincet

 

We are working on a solution but it will require a lot more testing to ensure we don't break other merchants.  In the short term, your options include re-enabling TLS 1.0 or using an HTTP relay response URL.

 

Richard

Hello everyone,

 

The solution for this issue will release today between 4-8pm Pacific.  Please retest after that time and let us know if you are successful receiving relay response posts with TLS 1.0 disabled on your server.

 

Richard

Hi @RichardH,

 

We just tested it today 6/26/2015 11:45 am cst.

 

The issue still remains.

To confirm, we enabled TLS 1.0 and it works.

Then we disabled TLS 1.0 and it stops working.

 

-Vince

@vincet Could you provide us with the ciphers you have enabled on the server you're expecting Relay Response on, please?

--
"Move fast and break things," out. "Move carefully and fix what you break," in.

Hi @Lilith

 

Here are what's enabled and disabled. Note that the only setting that changes is for TLS v1.0

 

Enabled:
TLS 1.1, 1.2
 
Disabled:
TLS 1.0
SSL 2.0, SSL 3.0

Hello @vincet

 

It would help to know the specific ciphers you have installed on your website, or the URL for your relay response for us to check.  If you are uncomfortable showing it here, just send an email to developer@authorize.net and reference this thread.

 

Thanks for your help on this issue.

 

Richard

@vincet, thanks, but those are the protocols you have enabled/disabled. Do you know which ciphers are used by those protocols? That's what we're hoping to find out, so we can confirm you have the same ciphers we do.

If you're using Windows Server, this Microsoft Developer Network article might help:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa374757(v=vs.85).aspx

--
"Move fast and break things," out. "Move carefully and fix what you break," in.