Hi Roland, your observations 1,2&3 are correct.
I have no provision to get to a standalone IBM JDK. Will be great if you can test it. I am using WAS 4.0.3 that comes along with WSAD 4.0.3 for testing my code. Here is a link that talks about using Sun JSSE with WAS 4.0.3 : http://www-106.ibm.com/developerworks/forums/dw_thread.jsp?message=49752&cat=10&thread=10122&forum=178 Thanks Regards NRR ( NRR stands for NR Ramanan) --- Roland Weber <[EMAIL PROTECTED]> wrote: > Hello NRR, (? :-) > > I'll try to summarize the situation... > (just went through the mailing list archive) > > 1. your code works fine with Sun JDK 1.4 standalone > 2. your code does not work with IBM JDK 1.3 in WSAD > with IBM JSSE > 3. your code does not work with IBM JDK 1.3 in WSAD > with Sun JSSE > > I'd like to narrow the origin of the problem > further: > > a) WSAD or IBM JDK? > Can you try to run your code in a standalone IBM JDK > 1.3, > without WSAD? Integrated development environments > tend > to do strange things to default settings and > locations of > configuration files. > > b) IBM JSSE or Sun JSSE > If you can test a), please do it with the default > configuration > (IBM JSSE) as well as after switching to the Sun > JSSE. Is > the IBM JSSE by default configured as a replacement > for > the Sun JSSE or as an additional provider? > > If you can't test with the IBM JDK standalone, > please let me know. > Sooner or later I'd have to tackle the SSL stuff > anyway, so I would > try to do it sooner. > > regards, > Roland > > > > > > > Ramanan nr <[EMAIL PROTECTED]> > 25.07.2003 22:17 > Please respond to "Commons HttpClient Project" > > To: Commons HttpClient Project > <[EMAIL PROTECTED]> > cc: > Subject: RE: SocketException : SSL > Implementation not > available > > > Hi Roland, > > I did check with the above steps you have mentioned. > hmmmm.. still I get the same exception. > > I created a new keystore, imported the cert, but for > some reason I am still getting > the ssl implementation not available exception. > > Should I create a new sslprotocolsocketfactory? If > so > can you point me to a sample. > If not, I am still unclear of what needs to be done > and can u throw some more light. > > Thanks > NRR > > --- Roland Weber <[EMAIL PROTECTED]> wrote: > > Hello, > > > > from the JavaDocs of > > javax.net.ssl.SSLSocketFactory.getDefault(): > > > > If SSL has not been configured properly for this > > virtual machine, > > the factory will be inoperative (reporting > > instantiation exceptions). > > > > > > In order to create SSL connections, the SSL > > implementation needs to > > know the root certificates it is supposed to > trust. > > This must be > > configured, > > usually in properties files. Since you are > switching > > manually to a Sun > > JSSE within an IBM JDK, chances are that there is > no > > configuration > > of the key store, which is supposed to hold the > root > > certificates. > > > > You should verify steps 7 and 8 of the > installation > > instructions: > > http://java.sun.com/products/jsse/install.html > > > > > > hope that helps, > > Roland > > > > > > > > > > > > > > > > Ramanan nr <[EMAIL PROTECTED]> > > 24.07.2003 22:32 > > Please respond to "Commons HttpClient Project" > > > > To: Commons HttpClient Project > > <[EMAIL PROTECTED]>, > > [EMAIL PROTECTED] > > cc: > > Subject: RE: SocketException : SSL > > Implementation not > > available > > > > > > Hi oleg, > > > > My https call. Works fine with Sun JDK 1.4.1 > > I dont have the provision to move to IBM's Version > > > > I am using commons-httpclient 2.0 beta, IBM JDK > > 1.3.1 > > (WSAD 4.0.3), Sun JSSE 1.0.3 > > > > I downloaded Sun JSSE 1.0.3 added the jar files > from > > that to WSAD JRE (to the ext directory) > > > > changed the security file to add the following > info: > > > > security.provider.1=sun.security.provider.Sun > > security.provider.2=com.sun.crypto.provider.SunJCE > > > security.provider.3=com.sun.net.ssl.internal.ssl.Provider > > security.provider.4=com.sun.jsse.JSSEProvider > > > #security.provider.5=com.ibm.crypto.provider.IBMJCE > > #security.provider.6=com.ibm.jsse.JSSEProvider > > > > Also in my code I am doing the following : > > > > > System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol"); > > Security.addProvider(new > > com.sun.net.ssl.internal.ssl.Provider()); > > Security.insertProviderAt(new > > com.sun.crypto.provider.SunJCE(),1); > > > > > > > > I am getting the following exception: > > > > java.net.SocketException: SSL implementation not > > available > > at > > > javax.net.ssl.DefaultSSLSocketFactory.createSocket(Unknown > > Source) > > at > > > org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:127) > > at > > > org.apache.commons.httpclient.HttpConnection.tunnelCreated(HttpConnection.java:749) > > at > > > org.apache.commons.httpclient.ConnectMethod.execute(ConnectMethod.java:204) > > at > > > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:638) > > at > > > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:500) > > <<stacktrace removed>> > > > > > > Am I missing any thing that needs to be done? > > > > thanks > > NRR > > > > > > > === message truncated === __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
