Re: Rule to access security
Re: Rule to access security
- Subject: Re: Rule to access security
- From: Jesse Tayler <email@hidden>
- Date: Mon, 23 Jan 2012 10:47:04 -0500
look at the part about rule caching
http://wiki.wocommunity.org/display/WO/The+D2W+Rule+System
to ensure a key's rules are fired each time the key is requested is referred to as a significant key, Wonder may have some advancements on this idea that someone might better explain, but it sounds like that is your problem.
On Jan 23, 2012, at 10:29 AM, Theodore Petrosky wrote:
> 100 : (pageConfiguration = 'ListPerson' and session.user.security.canEditPerson = 'true') => isEntityEditable = true [com.webobjects.directtoweb.BooleanAssignment],
>
>
> So I have this rule to access the security of my user. This must be wrong, because if I login as user1 and user1 has permission canEditPerson = true, when user2 logs in (and user2 canEditPeron = false) then user2 can edit the person EO. it is as if whoever was first wins and my app remembers.
>
> I even tried adding:
> 100 : (pageConfiguration = 'ListPerson' and session.user.security.canEditPerson = 'false') => isEntityEditable = false [com.webobjects.directtoweb.BooleanAssignment],
>
> What am I doing wrong?
>
> Ted
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden