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

Claus Ibsen commented on CAMEL-2987:
------------------------------------

Ashwin we need something similar to what Dejan did with AMQ
http://activemq.apache.org/encrypted-passwords.html

1)
A new camel component, camel-jasypt to contain the implementation to avoid 
having deps on 3rd party jars in camel-core

2)
A SPI interface in org.apache.camel.spi as neutral interface for this feature. 
So we can plugin and use other frameworks in the future.

3)
Hook into the Properties component from camel-core and use the pluggable SPI if 
it has been configured and leverage it to decrypt the text
(eg it scans for ENC( ) tokens), which I assume is a standard feature by Jasypt.

4)
Provide tooling in camel-jasypt like Dejan did, so you can run it from the cmd 
line to generate those tokens for your passwords

5)
Allow configuration of camel-jasypt to define algorithm and whatnot which is 
jasypt specific.
In fact it could just be a standard Camel component which you can use to 
encrypt/decrypt as well.

You have done these kind of components before. Then we can let end users use it 
for their messages as well.


> Allow encrypted passwords to be used in properties files
> --------------------------------------------------------
>
>                 Key: CAMEL-2987
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2987
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Ashwin Karpe
>             Fix For: Future
>
>
> We should add a feature to the properties component and simple language so it 
> can resolve encrypted usernames/passwords etc.
> We can use Jasypt as the library
> http://www.jasypt.org/
> And then add a prefix to the components component
> {code}
> foo.properties
> username=#ENC#4fg48dgh58747f744#ENC#
> {code}
> Just figuring our what the prefix/suffix tokens should be. Most likely 
> something better than {{#ENC#}}
> The simple language could have a built in function for this as well.

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

Reply via email to