RE: SSL in Java (was: Private CA 'jssecacerts' file location?)

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Friday, November 09, 2007 11:25 AM
To: Java Programming on and around the iSeries / AS400
Subject: SSL in Java (was: Private CA 'jssecacerts' file location?)

Ok, I'm forking this thread a bit ... because the thread nesting was
getting pretty distracting.

I've made a bit of progress ... although I'm not really happy with the
way I had to do it.

I got my test java app to talk to a my SSL server ... but I had to make
some modifications to the global java config that are fairly
unacceptable (especially since this is going to be used on a customers
system).

In the /QIBM/Proddata/java400/jdk14/lib/security/java.security file, I
made the following modifications:

-----------------------------
1. I added 'com.ibm.jsse.IBMJSSEProvider' as a security provider and
moved it to the top of the list. When it was at position 8 I still got
the cipher error.

#
# List of providers and their preference orders (see above):
#
# commented out by dmg 11/9/07
#security.provider.1=sun.security.provider.Sun
#security.provider.2=com.ibm.crypto.provider.IBMJCE
#security.provider.3=com.sun.rsajca.Provider
#security.provider.4=com.ibm.security.cert.IBMCertPath
#security.provider.5=com.ibm.as400.ibmonly.net.ssl.Provider
#security.provider.6=com.ibm.jsse.IBMJSSEProvider
#security.provider.7=com.ibm.security.jgss.IBMJGSSProvider
# added by dmg 11/9/07
#security.provider.8=com.ibm.jsse.IBMJSSEProvider

security.provider.1=com.ibm.jsse.IBMJSSEProvider
security.provider.2=sun.security.provider.Sun
security.provider.3=com.ibm.crypto.provider.IBMJCE
security.provider.4=com.sun.rsajca.Provider
security.provider.5=com.ibm.security.cert.IBMCertPath
security.provider.6=com.ibm.as400.ibmonly.net.ssl.Provider
security.provider.7=com.ibm.jsse.IBMJSSEProvider
security.provider.8=com.ibm.security.jgss.IBMJGSSProvider

2. I changed the ssl socketfactory providers to be the JSSE versions.

# commented out by dmg 9/11/07

#ssl.SocketFactory.provider=com.ibm.as400.ibmonly.net.ssl.SSLSocketFact
oryImpl

#ssl.ServerSocketFactory.provider=com.ibm.as400.ibmonly.net.ssl.SSLServ
erSocketFactoryImpl



# added by dmg 9/11/07

os400.jdk14.jst.factories=true

ssl.SocketFactory.provider=com.ibm.jsse.JSSESocketFactory

ssl.ServerSocketFactory.provider=com.ibm.jsse.JSSEServerSocketFactory


-----------------------------

I *THINK* that this configuration is using the
/QIBM/ProdData/Java400/jdk14/lib/security/jssacacerts file to pick up
my
CA certificate.

The test program works fine when I run it with a secofr profile ... but
when I run it with a normal programmer profile, I get
javax.net.ssl.SSLHandshakeException: unknown certificate :(

david

--
System i ... for when you can't afford to be out of business
--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.