WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

WC7, payment plugin and Authorize.Net AIM integration

  • 1.  WC7, payment plugin and Authorize.Net AIM integration

    Posted Fri April 15, 2011 07:43 PM
    Hello,

    Has anyone done any implementation on integrating a customized WC7 payment plugin with Authorize.Net AIM?  Specifically I'd like to find out some detailed SSL setup related information.  Here's the specific scenario I am having while attempting to establish a test connection to ANET's payment gateway (bear with me as this is my first time working with SSL on such a detailed level):

    1) Started WAS via RAD  (note that my RAD was originally "cloned" from another RAD instance, without any changes being made to the default-generated SSL keystore, truststore and such, hence the 'hostname' that's being referenced in the CN of the certificate is not the same as the actual host that I am running my WAS on.... my question, therefore, is if this could be the crux of my problem?)

    2) Created a self-signed personal certificate in the "NodeDefaultKeyStore"

    3) Retrieved a signer certificate from the external ANET test server for the "NodeDefaultTrustStore"

    4) On submitting a test order from my shopping cart, I do see the sequence of commands flowing correctly, until when the Apache HTTPClient (as called from inside the AIM stack) attempts to execute() (i.e. perform the actual HTTP post for our plugin), that an SSLPeerUnverifiedExceptions() gets thrown. 

    Does this imply the certificates are not trusted by the HTTPClient and if so, what should the proper procedure be in order to get my certificates set up correctly within my WAS?  Presumably all of the pieces involved are running from within the same JVM under such a scenario, but please clarify my understanding if it isn't right.

    Thanks in advance for any reply.

    Mary


  • 2.  WC7, payment plugin and Authorize.Net AIM integration

    Posted Thu May 05, 2011 02:51 AM

    Just a follow-up for folks who might need such info.  This problem has since been resolved.  The SSL certificate that was originally 'imported' from Authorize.Net into WAS trust store was not the correct one.  Once we found out the correct root certificate at Authorize.Net and added that into our WAS trust store, everything started working well.  The confusion occurred as the Authorize.Net server from which one should obtain the SSL certificate was not the same as that specified by the test server URL.