[
https://issues.apache.org/activemq/browse/AMQ-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-2007.
--------------------------------
Assignee: Dejan Bosanac
Resolution: Working as Designed
This is how XBean works, if there is a <plugins/> tag it will ignore the
attribute.
The workaround is to configure the plugin inside the <plugins/> tag with all
other plugins.
I've documented this a bit in a wiki (along with a simple example)
http://cwiki.apache.org/confluence/display/ACTIVEMQ/Developing+Plugins#DevelopingPlugins-ConfiguringpluginswithoutcustomXML
> XBean plugins override custom plugins instantiated with "plugins" attribute
> for broker
> --------------------------------------------------------------------------------------
>
> Key: AMQ-2007
> URL: https://issues.apache.org/activemq/browse/AMQ-2007
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: tested on Windows XP PC
> Reporter: Barbara Douthit
> Assignee: Dejan Bosanac
> Priority: Minor
>
> I am reporting what Dejan Bosanac has called a bug. This originated as the
> question/answers that follow:
> I am trying to use my custom authenticationPlugin (which installs a
> SimpleAuthenticationBroker) along with an XML definition for the
> authorizationPlugin as follows in the activemq.xml file:
> <bean id="MYAuthenticationPlugin"
> class="com.someplace.MYAuthenticationPlugin"/>
> <broker xmlns="http://activemq.apache.org/schema/core";
> brokerName="localhost" dataDirectory="${activemq.base}/data"
> plugins="#MYAuthenticationPlugin">
> <plugins>
> <authorizationPlugin>
> <map>
> <authorizationMap>
> <authorizationEntries>
> <authorizationEntry queue=">" read="ADMIN" write="ADMIN" admin="ADMIN"
> />
> <authorizationEntry queue="TOOL.>" read="USER" write="USER"
> admin="ADMIN" />
> <authorizationEntry topic=">" read="ADMIN" write="ADMIN" admin="ADMIN"
> />
> <authorizationEntry topic="TOOL.>" read="USER" write="USER"
> admin="ADMIN" />
> <authorizationEntry topic="ActiveMQ.Advisory.>" read="ADMIN,USER"
> write="ADMIN,USER" admin="ADMIN,USER"/>
> </authorizationEntries>
> <tempDestinationAuthorizationEntry>
> <tempDestinationAuthorizationEntry read="tempDestinationAdmins"
> write="tempDestinationAdmins" admin="tempDestinationAdmins"/>
> </tempDestinationAuthorizationEntry>
> </authorizationMap>
> </map>
> </authorizationPlugin>
> </plugins>
> ...
> </broker>
> The problem I have is when I define <plugins>, it takes over and
> MYAuthenticationPlugin isn't installed. Is there some way to put "two"
> plugins in the defintion for the <broker>? Or is there a way I can refer to
> MYAuthenticationPlugin in the <plugins> section? I have tried a lot of
> things with no success getting both of there pieces of the security pie.
> Any ideas would be greatly appreciated,
> Thanks,
> Barbara
>
> Re: authorizationPlugin and authenticationPlugin by Dejan Bosanac-3 Nov 18,
> 2008; 07:06am :: Rate this Message: - Use ratings to moderate (?)
> Reply | Reply to Author | Print | View Threaded | Show Only this Message
>
> It seems there is a bug in that XBean plugins override custom plugins
> instantiated with "plugins" attribute. Can you raise a Jira issue for this?
> Cheers
> --
> Dejan Bosanac
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
