Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-2307

old clients require separate security settings if they use the jms.topic or jms.queue prefix

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.6.3
    • Fix Version/s: 2.8.0
    • Component/s: None
    • Labels:
      None

      Description

      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.

       

      <acceptor name="artemis">tcp://0.0.0.0:61616}?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ryeats Ryan Yeats
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m