Github user jbertram commented on the issue:

    https://github.com/apache/activemq-artemis/pull/701
  
    The original use-case was related to Stomp durable subscriptions which in 
core terms is simply a durable, non-temporary queue.  Our Stomp implementation 
allows individual Stomp clients to connect to the same durable subscription by 
connecting with the same client-id and durable-subscription-name values, hence 
"sharing" the subscription.  The danger here is that a client which should not 
be allowed to connect to the durable subscription would in fact connect to it 
and essentially steal messages from the legitimate client.  However, by 
enforcing security on the individual queue that situation can be avoided.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to