Forum OpenACS Q&A: authorize-gateway, mystery error

Collapse
Posted by Torben Brosten on

After orders are confirmed, the following "SERVER's CERT is NOT VALID" error shows in the openacs-error.log. No connection event is logged at the payment processing's site. For non-gift-certificate orders (such as order 4000002), the error is repeated each 15 minutes for sometime over an hour (usualy tries for the default 8 hours).

[21/Dec/2003:07:55:45][43881.176942080][-sched:25-] Notice: Done running scheduled proc notification::sweep::sweep_notifications.
[21/Dec/2003:07:56:12][43881.146532352][-conn2-] Notice: nsopenssl: sockclient: SERVER's CERT is NOT VALID
[21/Dec/2003:07:56:12][43881.146532352][-conn2-] Error: Ns_PgExec: result status: 7 message: ERROR:  value too long for type character varying(400)

[21/Dec/2003:07:56:12][43881.146532352][-conn2-] Error: Wasn't able to do insert into authorize_gateway_result_log for transaction_id 4000003; error was Database operation "dml" failed
[21/Dec/2003:07:56:12][43881.146532352][-conn2-] Notice: Huh? redirecting: https://dekka.com:8443/ecommerce/gift-certificate-thank-you
[21/Dec/2003:07:56:44][43881.168057856][-sched:8-] Notice: Running scheduled proc acs_mail_lite::sweeper...

This gift certificate order 4000003 seems to have put a stop to 4000002 processing by taking precedence and stopping the scheduled authorize proc.

Your hints and suggestions much appreciated.

(I'm thinking admin error: wrong parameter value given, but which one and what form should it be)?

Collapse
Posted by Torben Brosten on
The mystery error (not logged in the authorize_gateway_result_log) has stopped since I revised parameter authorize_url's value.

I see that the code is automatically appending "?x_login" to authorize_url. I had not expected that.

The "SERVER's CERT is NOT VALID" message still occurs, but I'll see if I can track that down now.

Torben

Collapse
Posted by Bart Teeuwisse on
Torben,

the parameter authorize_url is the URL of the listening credit card processing application. The gateway concatenates all variables that need to be passed to Authorize.net to this base URL.

/Bart

Collapse
Posted by Torben Brosten on

Right. Thanks, Bart.

The 3rd pary docs (mis)state quite explicitly:

NOTE: Authorize.Net compatibility, POST to:

https://securefoodomain/barfilepath/foobarfile?x_Login

Note! [a statement stating the necessity of including "?" for passing cgi parameters] "?x_Login" is required for AuthorizeNet compatibility mode, native [non-authorize.net compatible] mode does not require this.

A suggestion has been added to bug list to help misled openACSers see the light of authorize-gatway's ease of use.