You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/01/17 16:26:00 UTC
[jira] [Commented] (ARTEMIS-3790) Support masked passwords when creating connections
[ https://issues.apache.org/jira/browse/ARTEMIS-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677832#comment-17677832 ]
ASF subversion and git services commented on ARTEMIS-3790:
----------------------------------------------------------
Commit bb8761fcd2d2d58223db960105056ef2af936069 in activemq-artemis's branch refs/heads/main from Ryan Highley
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=bb8761fcd2 ]
ARTEMIS-3790 Support masked JMS credentials
Adds standard username and password value unmasking for JMS
ActiveMQConnectionFactory instances
> Support masked passwords when creating connections
> --------------------------------------------------
>
> Key: ARTEMIS-3790
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3790
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.19.1
> Reporter: Apache Dev
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ActiveMQConnectionFactory#createConnection and similar APIs could accept "masked" passwords.
> This would improve usability in cases where connection password is already stored in masked format.
> For example, a client using TLS and username/password authentication would need to configure the "trustStorePassword" in the brokerURL - which accepts the ENC(...) form - and the connection password - currently not accepting the ENC(...) form.
> Accepting the masked password even for connection creation would improve usability for clients storing masked passwords in configuration files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)