camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohisa Igarashi (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10885) Add mask option to log EIP
Date Wed, 15 Mar 2017 13:29:41 GMT


Tomohisa Igarashi commented on CAMEL-10885:

Ah It doesn't have to do anything at CamelContext level, Log EIP/Component would just lookup
the LoggingStrategy instance from registry if it's not configured at processor level.

> Add mask option to log EIP
> --------------------------
>                 Key: CAMEL-10885
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Tomohisa Igarashi
>            Priority: Minor
> See nabble
> 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
> 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

View raw message