|
Yes I have gotten PFProJava to work from the 400 using JAVA 1.4. It took me several weeks of investigation and messing around with the files so I will try to remember everything I did. First I installed JAVA 1.4 on the 400 I also put SUN's jsse.jar from their 1.4 on the 400. I modified the security file java.security in /QIBM/ProdData/Java400/jdk14/lib/security 1. Changed list of providers: # # List of providers and their preference orders (see above): # security.provider.1=com.sun.net.ssl.internal.ssl.Provider security.provider.2=sun.security.provider.Sun security.provider.3=com.ibm.as400.ibmonly.net.ssl.Provider security.provider.4=com.ibm.jsse.IBMJSSEProvider security.provider.5=com.ibm.crypto.provider.IBMJCE security.provider.6=com.ibm.iseries.security.jgss.IBMJGSSiSeriesProvider security.provider.7=com.ibm.security.jgss.IBMJGSSProvider security.provider.8=com.ibm.security.cert.IBMCertPath security.provider.9=com.sun.net.ssl.internal.ssl.Provider 2. Changed default SSLSocketFactory and SSLServerSocketFactory to point to SUN's: # # Determines the default SSLSocketFactory and SSLServerSocketFactory # provider implementations for the javax.net.ssl package. # The Default ssl.SocketFactory.provider=com.ibm.as400.ibmonly.net.ssl.SSLSocketFactoryImp l ssl.ServerSocketFactory.provider=com.ibm.as400.ibmonly.net.ssl.SSLSocketFact oryImpl # I added os400.jdk14.jst.factories=true ssl.SocketFactory.provider=com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl ssl.ServerSocketFactory.provider=com.sun.net.ssl.internal.ssl.SSLServerSocke tFactoryImp Changed Envvar JAVA_HOME '/QIBM/ProdData/Java400/jdk14' PFPRO_CERT_PATH '/QIBM/ProdData/Java400/verisign/payflowpro/java/' CLASSPATH '/html/java:/QIBM/ProdData/Java400/verisign/payflowpro/java/:/QIBM/ProdData/ Java400/jdk14/lib/:/QIBM/ProdData/Java400/verisign/payflowpro/java/Verisign. jar:/QIBM/ProdData/Java400:/html/java/jsse.jar:/html/java/jcert.jar:/html/ja va/jnet.jar' I had to Do a change directory command so that the home directory was /QIBM/ProdData/Java400/verisign/payflowpro/java/ before running PFProJava I had to insure that port 443 was open on the 400 and our firewall. And that I had a DNS server defined to the 400 I think that was everything... Good luck -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of John Knox Sent: Tuesday, June 14, 2005 7:25 PM To: java400-l@xxxxxxxxxxxx Subject: RE: Verisign Payflow Pro Hi John. Glad to know somebody else is going through the same issues, and I'm excited to hear from you since it sounds like you're still in the middle of it. I am running the test program from the directory it resides in and the certs directory is one up from there. I did also verify that the path statement in the program also points to "certs". Couple of questions...what version of Java are you running? What test program are you running - the PFProJava? How far ahead of me are you? Did you get the test program to connect and get a response? Can you send me examples of your java.security file and anything else you think would be helpful? Thanks for your help! -----Original Message----- date: Mon, 13 Jun 2005 15:25:29 -0500 from: "Crocker, John" <john.crocker@xxxxxxxxxxx> subject: RE: Verisign Payflow Pro Try doing a change directory... Say your certificate is in /QIBM/ProdData/Java400/verisign/payflowpro/java/certs do this: CD DIR('/QIBM/ProdData/Java400/verisign/payflowpro/java') Assuming you left the statement in the Java program saying: pn.SetCertPath("certs"); I do have it working at least to their test sight. I am only slightly ahead if you. I went through all the same issues you did plus firewall issues and DNS issues.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.