Hi Andrew, Thanks a lot for your quick reply in the first place.
As I can see http://qpid.apache.org/andrew-acl-proposal.html explains how to write an ACL V2 file. I am not sure how to tell the broker where to look for the ACL file. Regarding the XML-based ACL I have used the sample configuration given in http://qpid.apache.org/java-xml-acls.html. My client is authorized to subscribe to topics, create temp queues, etc, when it's username different from what is given in the configurations, though. It does not allow my client to connect to the broker unless its username is mentioned under <access><users> in the config.xml. Thanks, Danushka On Mon, Jun 14, 2010 at 2:43 PM, Andrew Kennedy < [email protected]> wrote: > On 11 June 2010 14:53, Danushka Menikkumbura <[email protected]> wrote: > > Hi devs, > > > > I have configured the broker has explained in [1] but I do not see the > > clients being checked for authorization other than virtualhost-level > > permissions. I am using a trunk build. Please let me know if the doc is > > up-to-date and possible goofs that I may have made. > > > > [1] - http://qpid.apache.org/java-xml-acls.html > > Hi, > > Like Marnie says, look here for a description of the updated ACL v2 > syntax, as used in both the Java and C++ brokers: > http://qpid.apache.org/andrew-acl-proposal.html > > However, the XML syntax described at the pafge you cite (1) should > still work. Can you clarify what you mean about virtualhost-level > permissions vesus any others? > > Thanks, > Andrew. > -- > -- andrew d kennedy ? edinburgh : +44 7941 197 134 > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > >
