Hi Itai,
I'm sure there's something clever you could do here with
an attribute provider for you user object that supplied
__roles__ dynamically somehow, but I'd need to think
about that more... one easy way to limit who can
see different stuff is to use a wrapper around
your access methods
Steve Spicklemire wrote:
WITH [ QUERY ] LookupAttributesAndCheckForPermission(REQUEST) COMPUTE foo, bar, baz
where LookupAttributesAndCheckForPermission get's everything it needs out of
the REQUEST.
You could use
WITH CheckForPermission(REQUEST) and makeQuery() COMPUTE foo, bar, baz
Hi,
I'm trying to work out a security strategy for data stored in
Specialists, where specific users need access to specific data
instances.
For example: A Customer object is linked to a Person and Address
objects. The customer needs permission to edit the her - and only her
- Address
