You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to allow blacklisting instead of whitelisting, so we will mention the fields name to be masked and remaining fields will not be masked.
The text was updated successfully, but these errors were encountered:
@shahidmau We thought about this feature and decided to not add it to the lib. It's potentially dangerous. In the case of typo or misconfiguration with the whitelisting approach, you'll have the field masked and will not see the original value. In contrast to that with the blacklisting approach, the value can appear unmasked. It can bring lots of problems. For example, we stored our logs to the 3-rd party service for aggregation and had to be sure that customer PI information will not appear unmasked in these logs for any case.
Is there any way to allow blacklisting instead of whitelisting, so we will mention the fields name to be masked and remaining fields will not be masked.
The text was updated successfully, but these errors were encountered: