James.Strachan wrote:
>
> On 17/01/2008, jvr <[EMAIL PROTECTED]> wrote:
>>
>>
>> pplive wrote:
>> >
>> > BrokerService service=BrokerFactory.createBroker(new
>> > URI("xbean:activemq.xml"));
>> > service.setMessageAuthorizationPolicy(new
>> > MyMessageAuthorizationPolicy());
>> >
>> > am I worong ??
>> >
>>
>> Does this work yet?
>
> Yes - its fixed in trunk now.
>
Perfect - is it in Maven somewhere? I just tried 5.1-SNAPSHOT and it
doesn't seem to work. I'm configuring it through Spring and I know it's at
least loading the class because if I pass it a
non-MessageAuthorizationPolicy bean it balks. But messages still seem to
get through without going through the policy.
James.Strachan wrote:
>
>> Either I'm not using it right, or it's still broken in
>> 5.0.0 which is a little disappointing considering there's a bug 775 with
>> near exact details on what's wrong and how to fix.
>>
>> As a side question, does anybody implement a trusted host based model for
>> controlling access to an ActiveMQ broker? I can't find any information
>> on
>> how to do this. The MessageAuthorizationPolicy seemed promising, but I
>> can't get it to work as explicitly documented. I also see no way to get
>> the
>> sending host from the message once delivered to the consumer, but I'm new
>> to
>> JMS so maybe it's something simple.
>
> Yes, its something simple - but needs to be enabled...
>
> http://activemq.apache.org/jmsxuserid.html
>
This is useful, but ideally I would like to know the IP address or hostname
of the host that sent the message. I basically want to have a simple static
list of "allow these hosts to talk to the broker, disallow these hosts". I
would much prefer this be done at the application level and not the network
level via an e.g. firewall.
Thanks for your help!
--
View this message in context:
http://www.nabble.com/MessageAuthorizationPolicy-does-not-work---tp12248240s2354p14925066.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
