camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10885) Add mask option to log EIP and log component
Date Fri, 31 Mar 2017 23:54:41 GMT

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

ASF GitHub Bot commented on CAMEL-10885:
----------------------------------------

Github user igarashitm closed the pull request at:

    https://github.com/apache/camel/pull/1586


> 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)

Mime
View raw message