[SM-1029] Bug in HTTP BC when configuring managed keystore for SSL

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1.1
• Fix Version/s: 3.1.2, 3.2
• Component/s: servicemix-http

Environment

ServiceMix deployed on Windows XP

• Assignee: Guillaume Nodet
• Reporter: Will Franco
• Created: 14/Aug/07 13:03
• Updated: 06/Sep/07 16:28
• Resolved: 06/Sep/07 16:28

Description

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.