AMQ 7 / 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.

The CLI masking utilities should implement org.apache.activemq.artemis.cli.commands.ActionAbstract, Configurable, or some other interface that leverages the FileConfiguration and retrieve the configured codec from the broker configuration and use the default codec only in the absence of a configured custom coded classname.