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 to do the selector filtering.
Joe http://www.ttmsolutions.com - get a free ActiveMQ user guide njones wrote: > > 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 Security mechanism? I had a good > read over the web docs but I couldn't find a way to do this. > > Thanks > Nick. > > > Dejan Bosanac-3 wrote: >> >> 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/snyder/ >> Scripting in Java - http://www.scriptinginjava.net >> >> >> >> njones wrote: >>> Hi. >>> >>> We have a case at work where we want to disable the sending of messages >>> over >>> the stomp transport. Is this possible? >>> >>> I was looking at a custom BrokerFilter that overrides the send method >>> and >>> checks the connection info, but in my tests the Connection is being >>> stripped >>> out of the message at some stage during sending. It's there when I >>> create it >>> but gets lost along the way. >>> >>> I'm using version 5.2 >>> >>> Any help would be appreciated. >>> Thanks >>> Nick. >>> >> >> >> > > -- View this message in context: http://www.nabble.com/Disable-Stomp-transport-from-sending-messages-tp20774719p20811691.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
