Skip to content
Steve Hu edited this page Sep 25, 2016 · 1 revision

In the entire life cycle of the exchange, there might a lot of logging statements written to log files or other persistence storage. These logs will be used to assist production issue identifying and resolving and a wide group of people might have access to these logs. In order to reduce the risk of leak customer info, sensitive info needs to masked before logging. For example, credit card number, sin number etc.

Configuration

Given different API will have different sensitive data, the mask is configurable and can be applied at header, cookie, query parameters and body.

Mask with String

Mask with Regex

Mask with JsonPath