You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/31 02:13:41 UTC
[jira] [Commented] (CAMEL-10885) Add mask option to log EIP and log
component
[ https://issues.apache.org/jira/browse/CAMEL-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950195#comment-15950195 ]
ASF GitHub Bot commented on CAMEL-10885:
----------------------------------------
GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/1586
CAMEL-10885 A follow-up - masking formatter should be applied in all …
…process()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/igarashitm/camel CAMEL-10885-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1586.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1586
----
commit ef02fa49951713f9a7e0a9bb88bb67d0f5fa7ec6
Author: Tomohisa Igarashi <tm...@gmail.com>
Date: 2017-03-31T00:39:25Z
CAMEL-10885 A follow-up - masking formatter should be applied in all process()
----
> Add mask option to log EIP and log component
> --------------------------------------------
>
> Key: CAMEL-10885
> URL: https://issues.apache.org/jira/browse/CAMEL-10885
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Tomohisa Igarashi
> Priority: Minor
> Fix For: 2.19.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Mask-password-using-log-component-tp5794301.html
> We can add a mask option to the Log EIP. It would then take the toString to be logged, and then run a series of reg exp to search/replace sensitive information such as password and passphrase.
> We need to do this for key=value, xml and json format. So it kinda works on most common formats.
> We can then add this in the docs that this is what it can do, so users can use it as-is or not. Only if they have very special cases they would then need to write their own mask method and call as a bean from the log message.
> We can also add such functionality to the log component itself, eg <to uri="log:xxx">.
> So they reuse the same masking algorithm.
> See UriSupport which have masking for uris with key=value
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)