Hi Marnie, So, "properties" in "public Result authorise(Operation operation, ObjectType objectType, ObjectProperties properties)" should include the vhost name?. I do not see anything like that.
Thanks, Danushka On Wed, Mar 23, 2011 at 10:14 PM, Marnie McCormack < [email protected]> wrote: > Hi Danushka, > > The ACLs (v2) on the java broker are specified per virtual host, so the > queue permissions already have a 'namepsace' effectively. > > If you look at virtualhosts-systests-aclv2-settings.xml you'll see where > virtualhost level acl files get specified. Thus permissions for foo on > different vhosts get specified separately,and the call into authorise done > at the vhost level. > > Hth, > Marnie > > On Wed, Mar 23, 2011 at 3:27 PM, Danushka Menikkumbura < > [email protected]> wrote: > >> Hi Marnie, >> >> What I meant was having different access control settings for queue "foo" >> under vhost "vh1" and queue with the same name under vhost "vh2". I do not >> see vhost name as a parameter in authorize call. >> >> Thanks, >> Danushka >> >> On Wed, Mar 23, 2011 at 8:41 PM, Marnie McCormack < >> [email protected]> wrote: >> >>> Hi Danushka, >>> Yes - if you mean can we control virtualhost level access ? >>> >>> Details and examples are available here: >>> * >>> >>> https://issues.apache.org/jira/secure/attachment/12448750/Security-Plugins.pdf >>> * <https://cwiki.apache.org/confluence/display/qpid/andrew+acl+proposal> >>> >>> >>> >>> The XML for the docbook for this is in svn but doesn't seem to have been >>> rednered into the docbook for some reason. >>> >>> Thanks, >>> Marnie >>> >>> >>> On Wed, Mar 23, 2011 at 2:32 PM, Danushka Menikkumbura < >>> [email protected]> wrote: >>> >>> > Hi devs, >>> > >>> > Do we have $subject? >>> > >>> > Danushka >>> > >>> >> >> >
