That is exactly what I was finally planning to do. So, resource resolution
should be done inside my authz manager. I thought there was a neater way to
do it.
Thanks,
Danushka
On Fri, Jul 23, 2010 at 11:15 AM, Amila Jayasekara ami...@wso2.com wrote:
It seems to be you need to have a mapping
On Fri, Jul 23, 2010 at 9:00 AM, Danushka Menikkumbura danus...@wso2.comwrote:
Amila,
Anyways the issue is not about negative permissions. It can even be
something like let role A create queues that have names starting with
Temp_ as you just mentioned. How can we have something like that in
On Fri, Jul 23, 2010 at 2:28 PM, Amila Suriarachchi am...@wso2.com wrote:
On Fri, Jul 23, 2010 at 9:00 AM, Danushka Menikkumbura
danus...@wso2.comwrote:
Amila,
Anyways the issue is not about negative permissions. It can even be
something like let role A create queues that have names
Obviously we can not integrate these permission models. The only thing we
need to do is to share the User store between components. In Active
Directory case Carbon uses Active Directory users. But here I think you need
to let JMS Queue to use Carbon users and roles.
+1.
That is exactly
On Fri, Jul 23, 2010 at 2:52 PM, Danushka Menikkumbura danus...@wso2.comwrote:
Obviously we can not integrate these permission models. The only thing we
need to do is to share the User store between components. In Active
Directory case Carbon uses Active Directory users. But here I think you
Hi devs,
Inside my Carbon component I need to impose certain rules to restrict access
to JMS objects. For an example I need to say something like do not let user
A create JMS queues that have names starting with Temp_. I can handle the
rule language myself but how can I get the existing
On Thu, Jul 22, 2010 at 5:25 PM, Danushka Menikkumbura danus...@wso2.comwrote:
Hi devs,
Inside my Carbon component I need to impose certain rules to restrict
access to JMS objects. For an example I need to say something like do not
let user A create JMS queues that have names starting with
It seems to be you need to have a mapping with your rule and a resource
id. Cos in the permission model we authorize based on the resource id
(/x/y/z) etc ... I believe what you have given is only a single example.
Thus there can be many permutations? (like, name ending with Temp_ etc
...).
