Sun JSSE intergration with WebLogic

Question

First, I should state that I have been able to get my application to work in Tomcat
and run on it's own, but not in WebLogic.
Has anyone used Sun's JSSE implementation from within WebLogic? Is it possible
to do so?
I have set the following properties:
System.setProperty("java.protocol.handler.pkgs",
"com.sun.net.ssl.internal.www.protocol");
System.setProperty("javax.net.ssl.keyStoreType",
"pkcs12");
System.setProperty("javax.net.ssl.keyStore",
keystore);
System.setProperty("javax.net.ssl.keyStorePassword",
keyStorePassword);
System.setProperty("javax.net.ssl.trustStore",
trustStore);
System.setProperty("javax.net.ssl.trustStorePassword",
trustStorePassword);
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
I get the following exception when writing to the output stream of HttpsURLConnection:
java.io.IOExceptionWrite Channel Closed, possible SSL handshaking or trust failure
I am not that familiar with Weblogic, so any suggestions are welcome.

Answer 1

No, the loadLocalIdentity methods that take InputStream-s expect streams for the
certificate and the key pem files, with the key in pkcs8 format. If your certificate
is in pkcs12 keystore, you can read the cert and the key using java keystore api,
and then load them with the loadLocalIdentity(Certificate[], PrivateKey) method.
Pavel.
"Dave" <[email protected]> wrote:
>
Thanks for the response I appreciate it. I do have some follow up questions
you
may be able to help me with.
This application is performing two way SSL, but in this case my web app
(deployed
in WLS) is the client. Making a https call to public server that requires
the
client certificate. The public server issues the client certificates
in pkcs12
format. Can the weblogic.net.http.HttpsURLConnection class or WebLogic
SSL implementation
handle that format?
Thanks.
"tm" <no-reply> wrote:
From a coworker:
It sounds like in this particular case they are using an URL to open
the
connection.
On the server this will return a weblogic.net.http.HttpsURLConnection,
which
does not support the jsse configuration properties.
In the case of a one way connection they might be able to fix this by
setting weblogic.security.SSL.trustedCAKeyStore instead.
For two way they would need to use our HttpsURLConnection api to load
identity.
-tm
"tm" <no-reply> wrote in message news:[email protected]...
To the best of my knowledge, BEA doesn't test or claim to support
any
scenarios with Sun JSSE running inside a WLS server when the WLS serveris
setup to use SSL. However, it might work.
In any case, to see what WLS SSL is complaining about, turn on SSLdebug
tracing:
-Dssl.debug=true -Dweblogic.StdoutDebugEnabled=true
-tm
"Dave" <[email protected]> wrote in message
news:[email protected]...
First, I should state that I have been able to get my application
to
work
in Tomcat
and run on it's own, but not in WebLogic.
Has anyone used Sun's JSSE implementation from within WebLogic?
Is
it
possible
to do so?
I have set the following properties:
System.setProperty("java.protocol.handler.pkgs",
"com.sun.net.ssl.internal.www.protocol");
System.setProperty("javax.net.ssl.keyStoreType",
"pkcs12");
System.setProperty("javax.net.ssl.keyStore",
keystore);
System.setProperty("javax.net.ssl.keyStorePassword",
keyStorePassword);
System.setProperty("javax.net.ssl.trustStore",
trustStore);
System.setProperty("javax.net.ssl.trustStorePassword",
trustStorePassword);
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
I get the following exception when writing to the output stream
of
HttpsURLConnection:
java.io.IOExceptionWrite Channel Closed, possible SSL handshaking
or
trust
failure
I am not that familiar with Weblogic, so any suggestions are welcome.