You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Gregor Zurowski (JIRA)" <ji...@apache.org> on 2013/12/13 18:13:07 UTC

[jira] [Commented] (CAMEL-7067) JcrProducer should not store all exchange properties in the target JCR node

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

Gregor Zurowski commented on CAMEL-7067:
----------------------------------------

Pull request submitted: https://github.com/apache/camel/pull/67

> JcrProducer should not store all exchange properties in the target JCR node
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-7067
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7067
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jcr
>    Affects Versions: 2.12.2
>            Reporter: Gregor Zurowski
>         Attachments: CAMEL-7067.patch
>
>
> The CamelJcrInsert operation in JcrProducer stores all exchange properties in the target JCR node including all Camel properties that are found in the incoming exchange. This means that non-relevant data is persisted in JCR nodes including sensitive information such as username and password that is part of the URI in the CamelToEndpoint exchange property. Other examples of such properties include CamelJcrNodeName and CamelExternalRedelivered.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)