Return-Path: 
 <issues-return-19079-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 34C1311CAD
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Tue, 23 Sep 2014 02:48:34 +0000 (UTC)
Received: (qmail 80606 invoked by uid 500); 23 Sep 2014 02:48:34 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 80572 invoked by uid 500); 23 Sep 2014 02:48:33 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 80562 invoked by uid 99); 23 Sep 2014 02:48:33 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2014 02:48:33 +0000
Date: Tue, 23 Sep 2014 02:48:33 +0000 (UTC)
From: "Camel Guy (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12743265.1411407794000.100198.1411440513850@Atlassian.JIRA>
In-Reply-To: <JIRA.12743265.1411407794000@Atlassian.JIRA>
References: <JIRA.12743265.1411407794000@Atlassian.JIRA>
 <JIRA.12743265.1411407794294@arcas>
Subject: [jira] [Commented] (CAMEL-7849) Encrypted properties inside and
 outside <camelContext>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Camel Guy commented on CAMEL-7849:
----------------------------------

The Camel documentation for Jasypt reads like the examples work for both ${} and {}. It took me about 24 solid working hours to figure this out. This could just be a documentation problem. However, the downside is the additional CPU/memory overhead caused by loading the same .properties files multiple times. In my code, I load two properties files. Not a huge problem. The real problem is that this isn't as easy as it should be.

My real use case involves restlet realms. I want to encrypt user passwords. I also want to encrypt JDBC passwords. Therefore, I very much need ${} to work.

> Encrypted properties inside and outside <camelContext>
> ------------------------------------------------------
>
>                 Key: CAMEL-7849
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7849
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.13.2, 2.14.0
>            Reporter: Camel Guy
>            Assignee: Willem Jiang
>            Priority: Minor
>
> {noformat}
> File default.properties contains an entry like: key=ENC(..)
> The following Camel Spring DSL snippet decrypts the 
> property value inside <camelContext> via {{key}} but does 
> not decrypt it outside of the <camelContext> via ${key}:
> <bean id="jasypt" class="org.apache.camel.component.jasypt.JasyptPropertiesParser">
>     <property name="password" value="sysenv:PROPERTIES_KEY"/>
> </bean>
> <bean id="bridgePropertyPlaceholder" class=
>   "org.apache.camel.spring.spi.BridgePropertyPlaceholderConfigurer">
>   <property name="locations" >
>   <list>
>     <value>classpath:default.properties</value>
>   </list></property>
>   <property name='parser' ref='jasypt'/>
> </bean>
> In order to get ${} to decrypt, first I remove all of the above. 
> Then I add jasypt dependencies to pom.xml:
> <dependency>
>   <groupId>org.jasypt</groupId>
>   <artifactId>jasypt</artifactId>
>   <classifier>lite</classifier>
>   <version>1.9.2</version>
> </dependency>
>  <dependency>
>   <groupId>org.jasypt</groupId>
>   <artifactId>jasypt-spring3</artifactId>
>   <version>1.9.2</version>
>  </dependency> 
> And add the following to Camel Spring DSL:
> <bean id="environmentVariablesConfiguration"
>      class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig">
>    <property name="algorithm" value="PBEWithMD5AndDES" />
>    <property name="passwordEnvName" value="PROPERTIES_KEY" />
>  </bean>
>  <bean id="configurationEncryptor"
>      class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
>    <property name="config" ref="environmentVariablesConfiguration" />
> </bean>
> <bean id="propertyConfigurer" class=
>   'org.jasypt.spring3.properties.EncryptablePropertyPlaceholderConfigurer'>
>  <constructor-arg ref="configurationEncryptor"/>
>    <property name="locations" >
>   <list>
>     <value>classpath:default.properties</value>
>   </list></property>
> </bean>
> <bean id="jasypt" class=
>   "org.apache.camel.component.jasypt.JasyptPropertiesParser">
>     <property name="password" value="sysenv:PROPERTIES_KEY"/>
> </bean>
> <!-- And inside the camelContext... -->
> <camelContext xmlns="http://camel.apache.org/schema/spring">
> <propertyPlaceholder id="properties"
>  propertiesParserRef="jasypt" 
>  location="classpath:default.properties"/> 
> This is the only solution that I could discover. Using BridgePropertyPlaceholder 
> didn't work. <propertyPlaceholder> must be used inside <camelContext>.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)