[
https://issues.apache.org/activemq/browse/CAMEL-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Gargan closed CAMEL-2527.
---------------------------------
Resolution: Fixed
I've backed out the DSL changed from core and have made endpoints for them as
suggested. The new code will reside in camel-crypto (aka bouncycastle)
component. I'm closing this one and will add the patches for the component to
the bouncycastle feature ticket.
> Addition of DSL to sign and verify exchanges with Digital signatures.
> ---------------------------------------------------------------------
>
> Key: CAMEL-2527
> URL: https://issues.apache.org/activemq/browse/CAMEL-2527
> 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.
