On Thu, Jul 22, 2010 at 5:25 PM, Danushka Menikkumbura <[email protected]>wrote:
> 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 think first of all you should not try to write deny rules with security. Your rule should be some thing like this. Let roleA to create JMS Queues that have names starting with Temp_ Generally you can not hard code the user name in a software. you always should use the roles. and at runtime a user manger should create users and assign roles to them. In summary you need to think about the possible permissions to JMS Object and specify which roles have that permission. Anyway, Lets say you write this rule "do not let user A create JMS queues that have names starting with Temp_". How this rule get evaluated? Do you need to give the current users to JMS Object and will it evaluate the rule with any action? thanks, Amila. > I can handle the rule language myself but how can I get the existing > permission model to work with this?. I don't think the registry-based model > would help as we do not have resources attached in this case. > > Thanks, > Danushka > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
