You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Quinn Stevenson (Jira)" <ji...@apache.org> on 2021/02/24 01:52:03 UTC
[jira] [Commented] (AMQ-6941) Add option to allow anonymous
vm://xxx connections
[ https://issues.apache.org/jira/browse/AMQ-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289498#comment-17289498 ]
Quinn Stevenson commented on AMQ-6941:
--------------------------------------
Anonymous users didn’t work because enabling them made them available both inside the VM and from outside - that was too open for us. We wound up using the plugin mentioned below so that if you were connecting from inside the same JVM, you didn’t need a user or password - it fit our needs perfectly.
Quinn Stevenson
quinn@pronoia-solutions.com
(801) 244-7758
> Add option to allow anonymous vm://xxx connections
> --------------------------------------------------
>
> Key: AMQ-6941
> URL: https://issues.apache.org/jira/browse/AMQ-6941
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.11.4
> Reporter: Quinn Stevenson
> Priority: Minor
>
> When deploying JMS components in the same JVM as an ActiveMQ broker, it would be really nice to allow vm://broker-name connections to connect without a username/password.
> Either a new plugin could be added, or the Simple Authentication Plugin could be enhanced.
> There is a sample of a plugin that provides the basic functionality in my Github repository
> [https://github.com/hqstevenson/splunk-jms-activemq/tree/master/src/main/java/com/pronoia/splunk/jms/activemq/util]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)