Obfuscation
Rules
To enable obfuscation, connect.ems.obfuscation.fields have to be set. When this is set then connect.ems.obfuscation.method is required.
fix obfuscation converts the data to ***** for those fields required to obfuscate
only text (string) columns can be obfuscated.
the obfuscation process does not validate if the obfuscated path does not exist.
it supports nested structures as well
it supports arrays
When the data structure looks like this:
{ "a": { "b": "secret", ... }, "x": { "y": { "z": "another secret", ... } } }
set the value to be: a.b, x.y.z. This produces the following output:
{ "a": { "b": "*****", ... }, "x": { "y": { "z": "*****", ... } } }
When the data structure contains arrays, and the obfuscation logic needs to cover the array items then the path resolving the array should contain the keyword: value.
For example, given this data structure:
{ "a": [ "secret1", "secret2", ... ], "x": [ "y": { "z": "another secret", ... } ] }
then set the obfuscation to: a.value, x.value.y.z. This produces this output:
{ "a": [ "*****", "*****", ... ], "x": [ "y": { "z": "*****", ... } ] }