camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-3750) Provide a common mechanism to facilitate configuration of TLS across Camel components
Date Mon, 25 Apr 2011 02:48:05 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024709#comment-13024709
] 

Willem Jiang commented on CAMEL-3750:
-------------------------------------

Hi David,

Yes, you can replace the NS like the blueprint does, but it will introduce other issue that
there are two versions of JSSE parameters schema, one for spring and another for blueprint.
So I made some change on the camel-spring patch to let the JSSE parameters schema share the
same NS with camel-spring, and it is easy to update the camel-blueprint part.
 
BTW, I will commit the patch shortly after running the tests.

Willem

> Provide a common mechanism to facilitate configuration of TLS across Camel components
> -------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3750
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3750
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, camel-http, camel-jetty
>            Reporter: David Valeri
>            Assignee: Willem Jiang
>             Fix For: Future
>
>         Attachments: 2011.04.22-CAMEL-3750-camel-core-xml.patch, 2011.04.22-CAMEL-3750-camel-core.patch,
2011.04.22-CAMEL-3750-camel-http.patch, 2011.04.22-CAMEL-3750-camel-http4.patch, 2011.04.22-CAMEL-3750-camel-itest-osgi.patch,
2011.04.22-CAMEL-3750-camel-jetty.patch, 2011.04.22-CAMEL-3750-camel-spring.patch, CAMEL-3750-camel-core-xml.patch,
CAMEL-3750-camel-core.patch, CAMEL-3750-camel-http.patch, CAMEL-3750-camel-http4.patch, CAMEL-3750-camel-itest-osgi.patch,
CAMEL-3750-camel-jetty.patch, CAMEL-3750-camel-spring.patch, localhost.ks
>
>
> 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:
> {code}
> KeyStoreParameters ksp = new KeyStoreParameters();
> ksp.setResource(this.getClass().getClassLoader().getResource("jsse/localhost.ks").toString());
> ksp.setPassword(pwd);
> ksp.setContext(context);
>         
> KeyManagersParameters kmp = new KeyManagersParameters();
> kmp.setKeyPassword(pwd);
> kmp.setKeyStore(ksp);
> TrustManagersParameters tmp = new TrustManagersParameters();
> tmp.setKeyStore(ksp);
>         
> SSLContextParameters sslContextParameters = new SSLContextParameters();
> sslContextParameters.setKeyManagers(kmp);
> sslContextParameters.setTrustManagers(tmp);
> {code}
> XML Configuration:
> {code:XML}
> <SSLContextParameters id="sslContextParameters" secureSocketProtocol="TLS">
>   <keyManagers
>       keyPassword="password">
>     <keyStore resource="./localhost.jks" password="password"/>
>   </keyManagers>
>   <secureSocketProtocolsFilter>
>     <include>TLS.*</include>
>   </secureSocketProtocolsFilter>
> </SSLContextParameters>
> {code}
> Usage in a route:
> {code}
> from("jetty:https://localhost:443/hello?sslContextParametersRef=sslContextParameters").process(proc);
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message