camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Gargan (JIRA)" <>
Subject [jira] Commented: (CAMEL-2527) Addition of DSL to sign and verify exchanges with Digital signatures.
Date Tue, 09 Mar 2010 19:41:45 GMT


Stephen Gargan commented on CAMEL-2527:

I've got a good bit of the crypto component put together. Its pretty much just a fancy DataFormat
that does Symmetric encryption of the exchange payload. I need to put together the model object
in core to support it and it should be good to go. An example or two wouldn't hurt either.

I agree that a signing component would also be nice and it should be very easy to put together
on top of what is there. Do you feel the DSL is getting too overloaded? This really only adds
Sign and verify methods to the ProcessorBuilder. You don't see any of their configuration
DSL unless you use one of these so its not really that intrusive. A good ide with code completion
takes all the pain out of using the DSL no matter how rich it is.

 I really like how rich Camel's DSL is and am all for the richer the better, but will defer
to your judgement. Whats your call?

> Addition of DSL to sign and verify exchanges with Digital signatures.
> ---------------------------------------------------------------------
>                 Key: CAMEL-2527
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core, camel-spring
>            Reporter: Stephen Gargan
>            Priority: Minor
>             Fix For: 2.3.0
>         Attachments: signature-core.patch, signature-spring.patch, signature-wiki.txt
> I've put together and extension to the DSL that will enrich exchanges with a Digital
Signature cacluated using the payload. The signature is stored in a property of the exchange
and can be used to verify it at a later stage. It uses the JCE under the covers and It adds
the constructs 'sign' and 'verify' to the dsl. Basically it will allows you to do the following
> from("direct:sign").sign(somePrivateKey).to("direct:signaturetest");
> and later 
> from("direct:signaturetest").verify(somePublicKey).to(...);
> Keys can be supplied from keystores or in message headers for dynamic signing, the attached
wiki page explains the feature set in more detail. 
> The patch contains a binary keystore so to apply it you should run 
> patch -p0 --binary -i signature-core.patch
> Give it a try and see what you think. I'm also in the processor finishing up a CryptoDataFormat
that uses the JCE to encrypt and decrypt exchange payloads, its about 90% done and I should
get it out soon.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message