Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Sat, 2 Nov 2013 20:17:17 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12483761.1128092375000.11720.1383423437347@arcas>
In-Reply-To: <JIRA.12483761.1128092375000@arcas>
References: <JIRA.12483761.1128092375000@arcas>
Subject: [jira] [Resolved] (AMQ-376) security plugin which can use, say,
 LDAP to authenticate the user, then use a custom database table to
 associate roles to users and destinations to roles
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved AMQ-376.
-----------------------------

    Resolution: Won't Fix

We got a LDAP security plugin. 

And don't see the need for having roles stores in a RDBMS on the side.

> security plugin which can use, say, LDAP to authenticate the user, then use a custom database table to associate roles to users and destinations to roles
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-376
>                 URL: https://issues.apache.org/jira/browse/AMQ-376
>             Project: ActiveMQ
>          Issue Type: Wish
>            Reporter: james strachan
>
> BTW have added org.activemq.security.SecurityAdminMBean as a simple MBean API to the admin of these things.
> Note we wanna cache the security state; then have a notification (via JMS Topic) to flush/reload the data when folks change it - so performance is great and the security configuration is highly dynamic


--
This message was sent by Atlassian JIRA
(v6.1#6144)