camel-dev mailing list archives

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


Claus Ibsen commented on CAMEL-2527:

I wonder if we should add this in the core and have DSL for it.

If it was a component you can use it from recipient list, routing slip and whatnot as its
just an endpoint.
You can also more easily configure it as its just endpoint uris.

But of course DSL is also nice but we should also be a bit careful to not add to much in the
DSL as there is many many methods already.

And if its a separate component you can leverage commons-codec to get hold of a BASE64.

Yeah I totally agree SUN has been lame not to provide such a feature out of the box.
Just as I wish they have added a cron like scheduler. 

> 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