You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ryan Yeats (JIRA)" <ji...@apache.org> on 2019/04/15 16:06:00 UTC
[jira] [Created] (ARTEMIS-2307) old clients require separate
security settings if they use the jms.topic or jms.queue prefix
Ryan Yeats created ARTEMIS-2307:
-----------------------------------
Summary: old clients require separate security settings if they use the jms.topic or jms.queue prefix
Key: ARTEMIS-2307
URL: https://issues.apache.org/jira/browse/ARTEMIS-2307
Project: ActiveMQ Artemis
Issue Type: Bug
Components: ActiveMQ-Artemis-Native
Affects Versions: 2.6.3
Reporter: Ryan Yeats
Assignee: clebert suconic
We have a client who uses an older Artemis 1.1.0 client provided by an appserver. Even with the acceptor configured to handle prefix's we run into issues because the security policy still sees the jms.topic and jms.queue prefix. So we have to have additional security-setting configuration for each topic or queue.
{noformat}
<acceptor name="artemis">tcp://0.0.0.0:61616}?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)