Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6102961E7 for ; Wed, 6 Jul 2011 07:36:37 +0000 (UTC) Received: (qmail 40849 invoked by uid 500); 6 Jul 2011 07:36:36 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 40602 invoked by uid 500); 6 Jul 2011 07:36:26 -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 40593 invoked by uid 99); 6 Jul 2011 07:36:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jul 2011 07:36:23 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chubrilo@gmail.com designates 209.85.161.41 as permitted sender) Received: from [209.85.161.41] (HELO mail-fx0-f41.google.com) (209.85.161.41) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jul 2011 07:36:18 +0000 Received: by fxg9 with SMTP id 9so6074278fxg.28 for ; Wed, 06 Jul 2011 00:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=IYxG1EHbo2f242LSOHVDFneh00VV94K346LNhfUABRs=; b=xKvWHtKe/kFpBNc1IsTHHftKgAN2R2YcJDtkT23Z1secvPPda/COiJv77IVJJ8DAh3 U7l3nw+4taZI6mHXDubnXdPk4jtit3B6A4rR5AizlZ945ob/MnIj2jM3D4zPFwPaXuuY 1EXRrz0fjY/PtjaOoBkFkKEsQCqx4OqHlfcVY= MIME-Version: 1.0 Received: by 10.223.91.75 with SMTP id l11mr8275833fam.66.1309937756707; Wed, 06 Jul 2011 00:35:56 -0700 (PDT) Sender: chubrilo@gmail.com Received: by 10.223.95.193 with HTTP; Wed, 6 Jul 2011 00:35:56 -0700 (PDT) In-Reply-To: <1309889404500-3646693.post@n4.nabble.com> References: <1309889404500-3646693.post@n4.nabble.com> Date: Wed, 6 Jul 2011 09:35:56 +0200 X-Google-Sender-Auth: kya24sNmneYBaIxaJUKb7EQqTcU Message-ID: Subject: Re: Hot Reload authorizationPlugin from Config File From: Dejan Bosanac To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001517478f32aa9d7404a761a649 --001517478f32aa9d7404a761a649 Content-Type: text/plain; charset=ISO-8859-1 That's still not implemented. You can check alternatives, like LDAP based authorization. Also, all contributions are welcomed. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Jul 5, 2011 at 8:10 PM, Matt wrote: > I searched the archives and found this question asked before on this forum > in > 2006 ( > > http://activemq.2283324.n4.nabble.com/Refreshing-authorizationPlugin-config-td2343938.html > > http://activemq.2283324.n4.nabble.com/Refreshing-authorizationPlugin-config-td2343938.html > ) and again in 2009 ( > > http://activemq.2283324.n4.nabble.com/JAAS-authentication-issues-on-ActiveMQ-td2364908.html > > http://activemq.2283324.n4.nabble.com/JAAS-authentication-issues-on-ActiveMQ-td2364908.html > ), and in both cases the answer was "no". I am wondering, is there yet a > feature allowing ActiveMQ to reload the authorizationPlugin from the > activemq.xml config file without having to restart the broker? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Hot-Reload-authorizationPlugin-from-Config-File-tp3646693p3646693.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001517478f32aa9d7404a761a649--