[ 
https://issues.apache.org/jira/browse/ARTEMIS-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266369#comment-17266369
 ] 

ASF subversion and git services commented on ARTEMIS-3069:
----------------------------------------------------------

Commit 1f825ee424699b282f9f4b6fe5f0401616a9669b in activemq-artemis's branch 
refs/heads/master from Domenico Francesco Bruscino
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1f825ee ]

ARTEMIS-3069 Add option to mask using the configured password-codec


> Add option to mask using the configured password-codec
> ------------------------------------------------------
>
>                 Key: ARTEMIS-3069
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3069
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Domenico Francesco Bruscino
>            Assignee: Domenico Francesco Bruscino
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to