Does your consumer remain connected to the broker while/after you take Action 3? If so, this is expected behavior, because there is no capability to disconnect a previously-authorized client when they stop being authorized. But if that consumer disconnects and attempts to reconnect, I'd expect the attempt to be rejected.
Tim On Jan 16, 2018 6:46 AM, "docscaa" <docs...@gmail.com> wrote: > Team, > > I am implementing runtime reloading of authorization map settings in > activemq.xml using following configuration, > (http://activemq.apache.org/runtime-configuration.html) > > <broker xmlns="http://activemq.apache.org/schema/core"; start="false" ... > > <plugins> > <runtimeConfigurationPlugin checkPeriod="1000" /> > </plugins> > ... > </broker> > > I performed test cases out of which one specific case (critical) is not > working as expected. > Action 1 : After starting the broker with a User A without any map entry > for > test queue > Result 1: User A login Successful but not authorized to access test queue > > Action 2: then I modified the authorization map and allowed user A to read > and write on test queue > Result 2: User A login Successful and authorized on test queue > > Action 3: then I again modified the authorization map by removing the > access > of user A on test queue > Result 3: User A login successful and still authorized on the test queue, > which is here the problem is. User A should not be authorized on test > queue. > > I tried different ways and did a lot of troubleshooting for something if I > am missing. I believe there is something I am missing > > Thanks for the help > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
