topic Re: DPM and HTTPS relay in Integration and Testing

DPM and HTTPS relay

jasonmgeorge — Mon, 23 Apr 2012 18:39:06 GMT

Based on the documentation for DPM, it appears there is no issue with using an HTTPS address in "x_relay_url." I have DPM up and running with HTTP. When I switch my site over to HTTPS, which changes to the relay address to HTTPS, the relay does not compelete.

Any ideas where I could have gone wronog?

Re: DPM and HTTPS relay

RaynorC1emen7 — Mon, 23 Apr 2012 19:06:36 GMT

Do you have a valid SSL Certificates?

Can you access the https URL from outside of your network without getting any error?

Did you change the valid relay response URL in your merchant account setting?

Re: DPM and HTTPS relay

jasonmgeorge — Mon, 23 Apr 2012 19:06:57 GMT

Yep, SSL is valid (or at least Firefox recognizes the certificate as valid). I'm not really sure how to confirm that Authroize.net regonizes the certificate as valid.

I can access the HTTPS relay url from outside of the network without issue.

I have not set the valid relay response URL. The instructions did indicate that this was required, however, it was working just fine with HTTP without a relay repsonse URL.

I'm currently encoding some transaction information in the GET parameters of the relay url. I assume this won't work once I set the relay response URL. Is there some way I can encode custom field information in the POST relay response?

Re: DPM and HTTPS relay

RaynorC1emen7 — Mon, 23 Apr 2012 19:21:08 GMT

I have not set the valid relay response URL. The instructions did indicate that this was required, however, it was working just fine with HTTP without a relay repsonse URL.

I'm getting (14) The referrer, relay response or receipt link URL is invalid. If I didn't set the relay response URL as one of the valid URL.

Do you mean you didn't pass a "x_relay_url" on the form post? It mean you are using the default on your merchant account setting.

You can set merchant defined fields on the form post to https://???.authorize.net/gateway/transact.dll

http://developer.authorize.net/guides/SIM/Submitting_Transactions/Merchant-defined_Fields.htm

Re: DPM and HTTPS relay

jasonmgeorge — Mon, 23 Apr 2012 19:34:01 GMT

Oh, no I set "x_relay_url" in my form post. I did not set the "Default Relay Response URL" in my account settings.

Re: DPM and HTTPS relay

RaynorC1emen7 — Mon, 23 Apr 2012 20:01:26 GMT

And you didn't get the "(14) The referrer, relay response or receipt link URL is invalid" error?

Are you getting any error at all? Or it is just return a blank page?

Re: DPM and HTTPS relay

jasonmgeorge — Tue, 24 Apr 2012 02:59:09 GMT

I get the following message

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

      This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service.

Re: DPM and HTTPS relay

RaynorC1emen7 — Tue, 24 Apr 2012 11:43:42 GMT

Relay Response Basics and Troubleshooting pretty much summarized all the common problem.

If all you did is change it from HTTP to HTTPs and nothing else, not sure what else to test.

Can you tell if it even make it to your relay URL page?

Re: DPM and HTTPS relay

jasonmgeorge — Tue, 24 Apr 2012 18:10:27 GMT

It isn't making it back to my relay URL page. That's what I can't figure out. It makes it back just fine when my relay url is HTTP. As soon as I change it to HTTPS the relay fails.

Re: DPM and HTTPS relay

RaynorC1emen7 — Tue, 24 Apr 2012 19:27:50 GMT

Maybe it didn't like your SSL Certificates. Who the provider? and what type. could be the same problem as

http://community.developer.authorize.net/t5/Integration-and-Testing/SSL-cipher-suite-for-DPM-x-relay-url/m-p/21691

Re: DPM and HTTPS relay

RaynorC1emen7 — Wed, 25 Apr 2012 18:40:24 GMT

Was helping another user with a new test account.

I'm also getting

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

      This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service.

On the new account.

But on the old test account I'm getting

(14) The referrer, relay response or receipt link URL is invalid.

So, if it possible, even if you didn't do for HTTP, just log-in to your merchant and add your HTTPS URL to the valid URL. So we can rule it out as the problem.

Re: DPM and HTTPS relay

jasonmgeorge — Wed, 25 Apr 2012 19:26:36 GMT

The SSL certificate is a single domain, standard SSL from GoDaddy.

I obtained a script to test for the cypher's my site supports here

http://superuser.com/questions/109213/is-there-a-tool-that-can-test-what-ssl-tls-cipher-suites-a-particular-website-of

Here are the results

Obtaining cipher list from OpenSSL 0.9.8o 01 Jun 2010.
Testing ADH-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-SHA...YES
Testing DHE-DSS-AES256-SHA...NO (sslv3 alert handshake failure)
Testing AES256-SHA...YES
Testing ADH-AES128-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES128-SHA...YES
Testing DHE-DSS-AES128-SHA...NO (sslv3 alert handshake failure)
Testing AES128-SHA...YES
Testing ADH-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing ADH-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-ADH-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing ADH-RC4-MD5...NO (sslv3 alert handshake failure)
Testing EXP-ADH-RC4-MD5...NO (sslv3 alert handshake failure)
Testing EDH-RSA-DES-CBC3-SHA...YES
Testing EDH-RSA-DES-CBC-SHA...YES
Testing EXP-EDH-RSA-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EDH-DSS-DES-CBC3-SHA...NO (sslv3 alert handshake failure)
Testing EDH-DSS-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-EDH-DSS-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing DES-CBC3-SHA...YES
Testing DES-CBC-SHA...YES
Testing EXP-DES-CBC-SHA...NO (sslv3 alert handshake failure)
Testing EXP-RC2-CBC-MD5...NO (sslv3 alert handshake failure)
Testing RC4-SHA...YES
Testing RC4-MD5...YES
Testing EXP-RC4-MD5...NO (sslv3 alert handshake failure)
Testing DES-CBC3-MD5...NO (no ciphers available)
Testing DES-CBC-MD5...NO (no ciphers available)
Testing EXP-RC2-CBC-MD5...NO (sslv3 alert handshake failure)
Testing RC2-CBC-MD5...NO (no ciphers available)
Testing EXP-RC4-MD5...NO (sslv3 alert handshake failure)
Testing RC4-MD5...YES
Testing NULL-SHA...NO (sslv3 alert handshake failure)
Testing NULL-MD5...NO (sslv3 alert handshake failure)

I see DES listed a couple times. Do you happen to know which is the one that I need to have?

Re: DPM and HTTPS relay

jasonmgeorge — Wed, 25 Apr 2012 19:43:35 GMT

Ok, I added a Default Relay Response URL, which still genrates the

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

      This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service.

Re: DPM and HTTPS relay

RaynorC1emen7 — Wed, 25 Apr 2012 20:48:17 GMT

I see DES listed a couple times. Do you happen to know which is the one that I need to have?

Have to wait for one of the Mod for that.

What kind of logic do you have on the relay response page?

How long do it ususaly take before you see the "An error occurred while trying to ...." error? 5 seconds? 10 seconds?

Re: DPM and HTTPS relay

jasonmgeorge — Fri, 27 Apr 2012 20:59:29 GMT

I'm getting a response in 2-3 seconds.

My processing logic looks up the transaction from the database to verify that the details are valid (I supposed I could pass this off to the order complete page). It then records the transaction response to a log file, generates the redirect url and calls Authorize.net back with

echo AuthorizeNetDPM::getRelayResponseSnippet($returnUrl);

Somewhat as a side note, I've also noticed that running my site in HTTP is generating the following now

3,2,14,(TESTMODE) The referrer, relay response or receipt link URL is invalid.,000000,P,0,,,10.00,,auth_capture,,,,,,,,,,,,,,,,,,,,,,,,,,B97E73F8AE4861BC774223E9C5B01D78,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,Purchase

I'm not sure what's going on here, since I can access that page directly from the web.

Re: DPM and HTTPS relay

RaynorC1emen7 — Fri, 27 Apr 2012 22:13:43 GMT

If it timeout that fast, it probably mean authorize.net can't connect to your HTTPS page for some reason.

The 3,2,14 error is because I ask you to add the HTTPS to your valid relay response url. Remove it from your account and it should go away.

Re: DPM and HTTPS relay

jasonmgeorge — Tue, 15 May 2012 04:03:09 GMT

The issue does seem to be that authorize.net can't connect to my HTTPS page. I'm not having much luck figuring out why, however.

As far as I can tell, the relay response from authorize.net isn't hitting my server.

Based on the link you pointed out, I tried updating my settings to

SSLEngine on
SSLProtocol TLSv1
SSLCipherSuite AES:DES-CBC3-SHA
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

In the resulting ssl_request_log, I show that my checkout page is accessed through SSL, but the relay url request doesn't show up.

I can copy and past the x_relay_url from my checkout page in to the browser and it works just fine (and shows up in ssl_request_log).

Any ideas where I can go from here?

Re: DPM and HTTPS relay

Trevor — Wed, 16 May 2012 22:36:12 GMT

Actually, the error 14 that you are receiving doesn't indicate an error loading your relay response page, it is telling us that the relay response URL that you are submitting is not allowed for this account. By default, Authorize.Net accounts will allow developers to submit any relay response URL, but the account settings also allow you to specify a default relay response URL along with a longer list of allowed Response/Receipt URLs. Once you have configured these settings, it establishes a kind of whitelist of allowed relay response urls for the account.

The error that you are receiving indicates that at least one Response/Receipt URL has been specified in your account settings, and that it does not match what you are trying to use in your DPM request. There are two resolutions for this:

Add your relay response URL to the list of Response/Receipt URLs in your account settings.
Remove all of the URLs currently listed in your account settings so that once again any URL can be submitted. (This could cause a problem if some other software connecting to the account relies on the default URL being present.)