You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "Will F." <wi...@hotmail.com> on 2007/05/30 18:28:51 UTC

Bug in HTTP BC when configuring managed keystore for SSL

There is a bug in ServiceMixSslSocketConnector.  The problem is that
ServiceMixSslSocketConnector extends SslSocketConnector, and it is providing
its own data member and getter/setter for the trust store, named
"trustStore".  However, SslSocketConnector already declares a data member
and getter/setter for the trust store, named "_truststore".  

The bug is manifested in JettyContextManager.createServer(URL url,
SslParameters ssl) method, when the "managed=true" is included in your
SslParameters.   The initialization of the ServiceMixSslSocketConnector
calls "setTruststore" method which sets the "_truststore", eventually, there
is a call to  ServiceMixSslSocketConnector.createFactory() method, and in
its implementation, it passes in the value of the "trustStore" that has
never been set, instead of the value of "_truststore".

This bug is affecting the option of having a managed trust store for SSL.

This is bug was found in version 3.1.1
-- 
View this message in context: http://www.nabble.com/Bug-in-HTTP-BC-when-configuring-managed-keystore-for-SSL-tf3841442s12049.html#a10877360
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.