2009/6/25 Cezary Biele cezary.bi...@gmail.com:
i'd be grateful for any suggestions how this should be achieved the right
way using repoze.
The default supplied security policy consults the ``__acl__``
attribute; you could make this attribute dynamic (descriptor) and
grant permissions based on
Thanks for your reply!
could you please point me to some documentation?
cezary
On Thu, Jun 25, 2009 at 11:27 AM, Malthe Borch mbo...@gmail.com wrote:
2009/6/25 Cezary Biele cezary.bi...@gmail.com:
i'd be grateful for any suggestions how this should be achieved the
right
way using repoze.
2009/6/25 Cezary Biele cezary.bi...@gmail.com:
Thanks for your reply!
could you please point me to some documentation?
Try looking here:
http://docs.repoze.org/bfg/narr/security.html#assigning-acls-to-your-model-objects
\malthe
___
Repoze-dev mailing
Cezary said:
ps. i'm using repoze with pylons
Hold on, you're talking about the Web authorization framework *repoze.what*,
not the Web application framework *repoze.bfg*, right?
Cheers. :)
--
Gustavo Narea xri://=Gustavo.
| Tech blog: =Gustavo/(+blog)/tech ~ About me: =Gustavo/about |
Thanks for your answer Gustavo!
Just a quick question: what about repoze.who (using sql database) and
users/groups/permissions? is it also, like you said,optional? from what
I've seen in the docs for repoze.what quickstart, setup_sql_auth needs user,
group and permission class as arguments. but
