You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2019/04/15 16:28:00 UTC
[jira] [Commented] (ARTEMIS-2307) old clients require separate
security settings if they use the jms.topic or jms.queue prefix
[ https://issues.apache.org/jira/browse/ARTEMIS-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818148#comment-16818148 ]
Justin Bertram commented on ARTEMIS-2307:
-----------------------------------------
Can you clarify the specific use-case and behavior? The prefixes should be stripped for legacy clients so they should be using un-prefixed resources from the broker's perspective.
> 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
> Affects Versions: 2.6.3
> Reporter: Ryan Yeats
> Priority: Major
>
> 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)