You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Marius Thøring (JIRA)" <ji...@apache.org> on 2014/12/25 14:36:13 UTC

[jira] [Updated] (CAMEL-8183) JasyptPropertiesParser: Support for partially encrypted properties, custom encryptor

     [ https://issues.apache.org/jira/browse/CAMEL-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marius Thøring updated CAMEL-8183:
----------------------------------
    Description: 
*Support for partially encrypted properties:*
The proposed change allows for mixing encrypted and unencrypted content within a string (property value).

Previously the whole property had to be encrypted, example: 
{noformat}
Argument: ENC(123#def)
Result: somepass
{noformat}

With the proposed change the following is supported:
{noformat}
Argument: http://somehost:port/path?pass=ENC(123#def)&token=ENC(321#fed)
Result: http://somehost:port/path?pass=somepass&token=sometoken
{noformat}
An arbitrary amount of "ENC blocks" is supported.

*Support for specifying a custom encryptor:*
-Previously the encryptor was always instanciated within the method:
public StandardPBEStringEncryptor getEncryptor(). 
-A secret (password) as well as a custom encryption algorithm could be set using approperiate setter methods.
-I have now added a setter method for the encryptor:
public void setEncryptor(StandardPBEStringEncryptor encryptor)
-If an encryptor is set, the username and algorithm setter methods is ignored.
This change is useful when an encryptor is provided through an OSGI service, and the secret password is not known.

The proposed changes are available on github:
https://github.com/apache/camel/pull/357

Patch: https://github.com/apache/camel/pull/357.patch

  was:
*Support for partially encrypted properties:*
The proposed change allows for mixing encrypted and unencrypted content within a string (property value).

Previously the whole property had to be encrypted, example: 
{noformat}
Argument: ENC(123#def)
Result: somepass
{noformat}

With the proposed change the following is supported:
{noformat}
Argument: http://somehost:port/path?pass=ENC(123#def)&token=ENC(321#fed)
Result: http://somehost:port/path?pass=somepass&token=sometoken
{noformat}
An arbitrary amount of "ENC blocks" is supported.

*Support for specifying a custom encryptor:*
-Previously the encryptor was always instanciated within the method:
public StandardPBEStringEncryptor getEncryptor(). 
-A secret (password) as well as a custom encryption algorithm could be set using approperiate setter methods.
-I have now added a setter method for the encryptor:
public void setEncryptor(StandardPBEStringEncryptor encryptor)
-If an encryptor is set, the username and algorithm setter methods is ignored.

The proposed changes are available on github:
https://github.com/apache/camel/pull/357

Patch: https://github.com/apache/camel/pull/357.patch


> JasyptPropertiesParser: Support for partially encrypted properties, custom encryptor
> ------------------------------------------------------------------------------------
>
>                 Key: CAMEL-8183
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8183
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Marius Thøring
>            Priority: Minor
>
> *Support for partially encrypted properties:*
> The proposed change allows for mixing encrypted and unencrypted content within a string (property value).
> Previously the whole property had to be encrypted, example: 
> {noformat}
> Argument: ENC(123#def)
> Result: somepass
> {noformat}
> With the proposed change the following is supported:
> {noformat}
> Argument: http://somehost:port/path?pass=ENC(123#def)&token=ENC(321#fed)
> Result: http://somehost:port/path?pass=somepass&token=sometoken
> {noformat}
> An arbitrary amount of "ENC blocks" is supported.
> *Support for specifying a custom encryptor:*
> -Previously the encryptor was always instanciated within the method:
> public StandardPBEStringEncryptor getEncryptor(). 
> -A secret (password) as well as a custom encryption algorithm could be set using approperiate setter methods.
> -I have now added a setter method for the encryptor:
> public void setEncryptor(StandardPBEStringEncryptor encryptor)
> -If an encryptor is set, the username and algorithm setter methods is ignored.
> This change is useful when an encryptor is provided through an OSGI service, and the secret password is not known.
> The proposed changes are available on github:
> https://github.com/apache/camel/pull/357
> Patch: https://github.com/apache/camel/pull/357.patch



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