You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2022/05/09 20:01:00 UTC

[jira] [Resolved] (CXF-8699) Abillity to set sensitive filters on LoggingFeature

     [ https://issues.apache.org/jira/browse/CXF-8699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andriy Redko resolved CXF-8699.
-------------------------------
    Resolution: Fixed

> Abillity to set sensitive filters on LoggingFeature
> ---------------------------------------------------
>
>                 Key: CXF-8699
>                 URL: https://issues.apache.org/jira/browse/CXF-8699
>             Project: CXF
>          Issue Type: Improvement
>          Components: logging
>    Affects Versions: 3.4.7
>            Reporter: Julien Greffe
>            Priority: Major
>             Fix For: 4.0.0, 3.6.0, 3.5.3, 3.4.8
>
>
> Hello,
> class {{LoggingFeature}} has new methods to add sensitive filters on custom LoggingFeature:
> {code}
> addSensitiveElementNames
> addSensitiveProtocolHeaderNames
> {code}
> Currently, we can't configure the default LoggingFeature to filter sensitive informations from scratch through configuration.
> More, we can't change configuration to update filters and have them reflected on default LoggingFeature.
> Idea is to:
> - add two methods
> {code}
> setSensitiveElementNames
> setSensitiveProtocolHeaderNames
> {code}
> - add two configuration keys:
> {code}
> sensitiveElementNames
> sensitiveProtocolHeaderNames
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)