Implementing the Obfuscator interface in an entity

To be obfuscatable, an entity must implement the Obfuscator interface and specify an implementation class other than UnsupportedObfuscator. For example, use a class that extends DefaultPersonalDataObfuscator.

The entities that have Obfuscator implementations that support obfuscation are:

Credential – CredentialDefaultObfuscator
Has fields and typekeys marked PersonalData.
OfficialID – DefaultPersonalDataObfuscator
Has fields and typekeys marked PersonalData.
User – UserDefaultObfuscator
Has fields and typekeys marked PersonalData.
UserContact – UserContactDefaultObfuscator
This entity is a subtype of Person, which is a subtype of Contact. It inherits the Contact implementation of the Obfuscatable delegate and overrides the Contact implementation of the Obfuscator interface. In the base configuration, the EmployeeNumber field is marked PersonalData.

The following entities implement the Obfuscatable delegate, and in the base configuration their Obfuscator interface implementation is UnsupportedObfuscator:

Address
Contact – Has fields and typekeys that are marked PersonalData.
ContactCategoryScore
Contact.Global
Person – Inherits obfuscation settings from Contact. Has fields and typekeys that are marked PersonalData.