it may be tricky, simplest may be to cycle the broker when permissions are
removed or remove/add the transportconnector such that all connections
recycle.
There are no system topics that allow modification in that way, the
advisory topics are read only.
JMX gives an alternative route to explore if
That's a bit strange behaviour for me, especially because ActiveMQ Artemis
disconnets such clients in the same situation..
But could you provide some tips, how can I configure my code for doing that
manually? Does some system topic exist where I can send a disconnect signal
for the specified consu
That is as expected. There auth happens at new connection time, there is
nothing that tracks existing connections and boots them out.
On Tue, 5 Dec 2017 at 22:52 zaptos wrote:
> Hello!
> I've been configured ActimeMQ as MQTT broker using
> *jaasAuthenticationPlugin
> & runtimeConfigurationPlugin
Hello!
I've been configured ActimeMQ as MQTT broker using *jaasAuthenticationPlugin
& runtimeConfigurationPlugin* features, but unfortunately I have an issues
when I don't understand - is it a bug or feature in ActiveMQ:
1) There is a configured user *test *with password *testpass*. The ActiveMQ
i
