Here is what I have found. The trusted certificate error comes from HttpClient.java/HttpClientException.java.
In HttpClient.java I changed trustAny from trustAny=false to trustAny=true. This gets us by for testing with Authorize.net test servers. Not sure if it will fly in production without a "trusted" certificate, or whether that cert must be signed by a CA. Anyone? ----- Original Message ----- From: "BJ Freeman" <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, November 27, 2007 4:59:21 PM (GMT-0700) America/Denver Subject: Re: POS and Authorize.net error Oh the ver 4.0 has the cvv code but the trunk does not. BJ Freeman sent the following on 11/27/2007 3:57 PM: > there are differences between the one in the ver 4.0 and trunk > both were updated about the same day. . > the trunk one checks further to see if the test property is null > if it is then it returns test is true. > where ver 4.0 looks only for a TRUE to mark it as a test. > if null will allow the processes to run as non test. > > David E Jones sent the following on 11/27/2007 2:58 PM: >> On Nov 27, 2007, at 3:38 PM, Vince M. Clark wrote: >> >>> No. Once I realized I had a cert issue I started reading up on related >>> ML postings and the Technical Production Setup Guide. >>> >>> In the past we were running on OpenTaps when we setup Authorize.net. I >>> guess all the SSL config is already done for you in Open Taps because >>> we never had to mess with it. >> Actually I think this is a new feature, and one recently required by >> Authorize.net because they had some cut-off date after which they would >> not process transactions without an encrypted connection. >> >> -David >> > > >
