The native security plugins are designed only to authenticate and authorize
clients; they can't be configured to perform your custom filtering. I'd rely
on the native security plugins to authenticate the clients and restrict
their access to destinations and then plugin your customer BrokerFilter t
We are also using the custom Filter to validate that a user subscribes with a
selector that matches a regular expression we define. So I decided to have
the Filter serve the second purpose as well of blocking the sending of
messages from a Stomp client.
Could all this be done via the native Secu
Hi,
why don't you just use standard ActiveMQ security mechanism; connect
Stomp clients with the appropriate credentials and give read-only access
to destinations?
Cheers
--
Dejan Bosanac
http://www.ttmsolutions.com - get a free ActiveMQ user guide
ActiveMQ in Action - http://www.manning.com/
