Based on my current understanding of the management functionality I would
expect your configuration to reliably secure the DLQ so I would consider
any failure to do so a bug. Please open a JIRA and include a test-case to
reproduce the issue.
Justin
On Wed, Mar 21, 2018 at 1:29 PM, cnadukula wr
any update for me on this guys?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
hi Justin,
just wanted an insight on what i was doing.
We are trying to disable curl/hawtio access to one of our production artemis
instances and only to dead letter queue. I tried one of the suggestions that
you had put in
http://activemq.2283324.n4.nabble.com/Disable-access-to-Dead-Letter-Queue
hi guys,
any update for me on this?
Thanks,
CHandra
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Thanks Justin for the response. But please correct me if i am wrong, I added
the following to management.xml file
I put in the queue as DLQ and access method as anything and assigned no
roles to it. Is this the right way to do it?
If not could you please guide me the right way.
> like people cannot retrieve the message either from hawt or using curl
command either.
If you need to secure a particular management operation you can use the
security functionality added in Artemis 2.4.0 via ARTEMIS-1463 [1].
Documentation is available here [2].
Justin
[1] https://issues.apa
