Just FYI, apparently, you cannot specify the Java SSL encryption providers dynamically in the code of a web application running under Weblogic.
for example: Security.insertProviderAt(new com.sun.net.ssl.internal.ssl.Provider(), 2); The dynamic declaration gets ignored because Weblogic only looks to the jdk1.x/jre/lib/security/java.security file for it's list of providers. You must list your providers statically in this file. This fixed my problem. I can now run a SOAP client under Weblogic and make calls over SSL. > -----Original Message----- > From: Mike Ferraro [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 25, 2003 11:54 AM > To: [EMAIL PROTECTED] > Subject: SOAP+SSL+Weblogic6.1=javax.net.ssl.SSLException: Can't support > cipher suite [0, 5] > > > First, > I saw the message "SSL messages via Apache SOAP/Weblogic 6.1" in the > archives. Marty, I believe that Daniel is correct. You are missing > certificates for your client and server to be able to > authenticate with each > other. I ran into that second exception when I specified the > wrong location > for my client keystore. > > Second, > I need help! I'm am trying to run an Apache SOAP client in Weblogic 6.1 > over a secure SSL connection. I have successfully run the same exact code > in a standalone app, but when I run it under Weblogic I get this > exception: > > javax.net.ssl.SSLException: Can't support cipher suite [0, 5] > > The stacktrace looks something like: > > [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: > javax.net.ssl.SSLException: Can't support cipher suite [0, 5]; > targetException=java.lang.IllegalArgumentException: Error opening socket: > javax.net.ssl.SSLException: Can't support cipher suite [0, 5]] > at > org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPCon > nection.ja > va:354) > at org.apache.soap.rpc.Call.invoke(Call.java:248) > ... > ... > ... > > Does anyone know what is wrong and how I can fix it? > > ~mike > > >
