[
https://issues.apache.org/jira/browse/CAMEL-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927677#comment-15927677
]
Claus Ibsen commented on CAMEL-10885:
-------------------------------------
Yeah I suggest to do the interface and get a basic implementation that only
works with the Log EIP.
Then we look at the global thing afterwards as it touches upon the log
component etc. And maybe other places where we do logging.
As the log component uses a different interface called ExchangeFormatter to log
its message. So log EIP and log component are not using any shared logic.
And then later we can look at find a good spot for some kind of easy switch to
turn on mask in logging on|off. And allow to plugin a custom implementation of
the search/replace.
> Add mask option to log EIP
> --------------------------
>
> 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
>
> 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)
