[
https://issues.apache.org/jira/browse/CAMEL-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926132#comment-15926132
]
Tomohisa Igarashi commented on CAMEL-10885:
-------------------------------------------
Hi [~davsclaus],
How about adding LoggingStrategy or something at CamelContext level so that it
can be configured at once? then add strategy option to the Log EIP/Component to
override for each invocation. We can add keyvalue/xml/json mask into
DefaultLoggingStrategy so it can be used OOTB. To be backward compatible,
LoggingStrategy should be NO-OP by default though.
> 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)
