Re: Unwanted caching of authorization results

2017-04-07 Thread Tim Bain
Thanks for giving this guidance for anyone who wants to do this in the future. If you'd like to have a less hacky (i.e. config file based) way to do this in a future version of ActiveMQ, please submit an enhancement request in JIRA. If you do, please copy and paste the workaround you just describe

Re: Unwanted caching of authorization results

2017-04-07 Thread Vince Cole
OK, so I am answering my own question here (instead of just deleting it all) in case it might be of help to someone... I have solved it by doing the following: * decorate the class SecurityContext * in the decorator, override method getAuthorizedWriteDests * in that method, always return an empty

Re: Unwanted caching of authorization results

2017-04-06 Thread Vince Cole
Sorry, forgot to say: I am using ActiveMQ 5.14.0 and developing my own plugins. Trying to write a plugin to deliver same functionality as AuthorizationMap, but as a proper plugin (i.e. using BrokerFilter, etc) so it can read a few bean properties from activemq.xml on startup. Also the message fro