Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 1FD8A180630 for ; Tue, 2 Jan 2018 20:47:50 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 01006160C26; Tue, 2 Jan 2018 19:47:50 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 45499160C09 for ; Tue, 2 Jan 2018 20:47:49 +0100 (CET) Received: (qmail 75852 invoked by uid 500); 2 Jan 2018 19:47:48 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 75841 invoked by uid 99); 2 Jan 2018 19:47:48 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2018 19:47:48 +0000 Received: from mail-ot0-f172.google.com (mail-ot0-f172.google.com [74.125.82.172]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C1B411A00AE for ; Tue, 2 Jan 2018 19:47:47 +0000 (UTC) Received: by mail-ot0-f172.google.com with SMTP id 14so16095267oth.9 for ; Tue, 02 Jan 2018 11:47:47 -0800 (PST) X-Gm-Message-State: AKGB3mK958EVVw28NFIwZR6FdqpQOoEY2ytmuq/IsCJxmcR91LjacQ2J mNZpQhWjH78/SmxGwVZfJUgtk5npQ4FeOl49AL64kA== X-Google-Smtp-Source: ACJfBosR61yoRWTDJQSuyiAXsjw+TkmoZLMAggwlb66n5NuJxxVLtPeL/D3IerV0aRtEUPtuuIxPGh69wX/UFJAgGhc= X-Received: by 10.157.87.46 with SMTP id p43mr37735554oth.319.1514922466996; Tue, 02 Jan 2018 11:47:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.77.15 with HTTP; Tue, 2 Jan 2018 11:47:46 -0800 (PST) In-Reply-To: <1514920830420-0.post@n4.nabble.com> References: <1514920830420-0.post@n4.nabble.com> From: Justin Bertram Date: Tue, 2 Jan 2018 13:47:46 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Disable access to Dead Letter Queue To: users@activemq.apache.org Content-Type: multipart/alternative; boundary="001a114f03a882095f0561d05f9b" archived-at: Tue, 02 Jan 2018 19:47:50 -0000 --001a114f03a882095f0561d05f9b Content-Type: text/plain; charset="UTF-8" > 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.apache.org/jira/browse/ARTEMIS-1463 [2] https://activemq.apache.org/artemis/docs/latest/management.html (see the "Role Based Authentication with JMX" section) On Tue, Jan 2, 2018 at 1:20 PM, cnadukula wrote: > Hi, > > as part of a security concern that we have, I was wondering if there is any > way that we can disable access to Apache Artemis's Dead Letter queue, all > together. like people cannot retrieve the message either from hawt or > using > curl command either. Please let me know. > > Thanks, > Chandra > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html > --001a114f03a882095f0561d05f9b--