[
https://issues.apache.org/jira/browse/CXF-9164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016634#comment-18016634
]
Freeman Yue Fang commented on CXF-9164:
---------------------------------------
Hi [~mdiskin],
Please see this commit
https://github.com/apache/cxf/commit/cb0fc820574af0c0a707fd84a49dad1e083f283e
which demonstrates how this AttributeMaskingHelper should be.
For the backward compatibility concern(new method added into API), we can
consider to change the default MaskSensitiveHelper behaviour(to support
attribute mask OOTB) in CXF 4.2 release.
Cheers
Freeman
> Logging Feature - Sensitive attributes (not elements) are not masked
> --------------------------------------------------------------------
>
> Key: CXF-9164
> URL: https://issues.apache.org/jira/browse/CXF-9164
> Project: CXF
> Issue Type: Bug
> Components: logging
> Affects Versions: 4.1.3
> Reporter: Mark Diskin
> Assignee: Freeman Yue Fang
> Priority: Major
>
> I see that protocol headers and element <a>...</a> are masked but regular
> attributes are not e.g.
> {code:java}
> <ns2:entity description="Voluntary Cancellation" entityTypeId="1" id="9"
> sortOrder="9" templateDocId="090027b0801d5969"/>{code}
> templateDocId is not set to XXX.
> below is the code I used:
> {code:java}
> private static LoggingFeature getLoggingFeature() {
> LoggingFeature loggingFeature = new LoggingFeature();
> loggingFeature.addSensitiveProtocolHeaderNames(new
> HashSet<>(List.of("CT-REMOTE-USER")));
> loggingFeature.addSensitiveElementNames(new
> HashSet<>(List.of("username","orgID","templateDocId")));
> loggingFeature.setPrettyLogging(true);
> loggingFeature.setLogBinary(false);
> loggingFeature.setLogMultipart(false);
> return loggingFeature;
> } {code}
> Hoping this is a correctable oversight or some error I did (I checked for
> addSensitiveAttributeNames method )
> Thanks
> Mark
--
This message was sent by Atlassian Jira
(v8.20.10#820010)