camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Valeri (JIRA)" <>
Subject [jira] Created: (CAMEL-3750) Provide a common mehanism to facilitate configuration of TLS across Camel components
Date Thu, 03 Mar 2011 20:35:36 GMT
Provide a common mehanism to facilitate configuration of TLS across Camel components

                 Key: CAMEL-3750
             Project: Camel
          Issue Type: Improvement
          Components: camel-core, camel-http, camel-jetty
            Reporter: David Valeri

CXF provides a nice Spring Namespace handler for configuring TLS options on the Jetty transport.
 Configuring these options using XML in Spring or through a simplified set of utility classes
decreases the learning curve for users by sheltering them from the horrors of JSSE.

There are a large number of components in Camel that deal with socket communication at some
level, but they all require users to learn the specific low level configuration capabilities
of the library on which the component is based in order to configure custom TLS options.

It would be convenient if users didn't need to learn the advanced networking configuration
options for each component.

This enhancement suggests a similar Spring Namespace handler and utility classes that allow
for simplified configuration of an SSLContext as well as adding provisions to some of the
Camel components in order to accept this new configuration mechanism.  The initial components
to support the new configuration mechanism are the http, http4, and Jetty components.  Other
components would follow.

An example usage is below.

Programmatic configuration:

KeyStoreParameters ksp = new KeyStoreParameters();
KeyManagersParameters kmp = new KeyManagersParameters();

TrustManagersParameters tmp = new TrustManagersParameters();
SSLContextParameters sslContextParameters = new SSLContextParameters();

XML Configuration:

<SSLContextParameters secureSocketProtocol="TLS">
    <keyStore resource="./localhost.jks" password="password"/>

Usage in a route:


This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message