Just go to the https://issues.apache.org/activemq/, register and hit "Create New Issue".
I think your solution will work, but it will be better definitely to have it configured in activemq.xml Cheers babsD wrote: > Hi Dejan, > > Thanks a lot for taking a look at this. I am not sure how to "raise a Jira > issue" - this is my first time ever emailing a problem to any site. If you > can help with this, please let me know what I should do. In the meantime, I > wrote an AuthorizationPlugin and call its installPlugin method inside the > MYAuthenticationPlugin.installPlugin method, so the broker now seems to have > both authentication and authorization information now. Not sure this is > really OK to do? I would have preferred to have the authorization > information in the activemq.xml file where I can change it. > > Thanks, > Barbara > > > Dejan Bosanac-3 wrote: > >> 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 >> >> >> http://www.ttmsolutions.com - get a free ActiveMQ user guide >> >> ActiveMQ in Action - http://www.manning.com/snyder/ >> Scripting in Java - http://www.scriptinginjava.net >> >> >> >> babsD wrote: >> >>> Hi, >>> >>> 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 >>> >>> >>> >> >> > > -- Dejan Bosanac http://www.ttmsolutions.com - get a free ActiveMQ user guide ActiveMQ in Action - http://www.manning.com/snyder/ Scripting in Java - http://www.scriptinginjava.net