Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Artemis documentation describes how to implement and configure a custom codec class by extending the SensitiveDataCodec class, adding the new class to the classpath, and configuring a custom-codec element in the broker configuration; however, there does not seem to be any provision in the masking utility classes to retrieve and use the custom codec. Instead, the masking utility is hard-coded to return the DefaultSensitiveStringCodec bundled with the broker.
Attachments
Issue Links
- links to