Approach for masking sensitive information in log statements. - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

We are using inbuilt custom logging processor to log body of Exchange. Due to PCI compliance I have to redact sensitive information like creditcard,ssn,etc., Because I have to parse the whole message and construct with redacted body I am looking for nonblocking invocation of the processor. I found couple of approaches 1. implementing AsyncProcessor and StaticWireTap. Which among them is the best suited for my requirement ?

Environment

Red Hat JBoss Fuse Service Works
- 6.2.1
Red Hat JBoss Enterprise Application Platform (EAP)
- 7.x
- 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)