On Nov 27, 6:03 am, Gustavo Narea <[EMAIL PROTECTED]> wrote:
> Hello, everybody.
>
> I'm writing to let you know about the authorization framework I have been
> working on, repoze.what:http://static.repoze.org/whatdocs/
>
> Some of its features are:
> * Web framework independent.
> * Authorization only. It will only do authorization and nothing else.
> * _Highly_ extensible.
> * _Fully_ documented.
> * Your application's `groups` and `permissions` may be stored in an SQLAlchemy
> managed database, thanks to the SQL plugin (repoze.what.plugins.sql).
> * The only requirement is that you use the repoze.who authentication framework
> (which is configured for you by repoze.what).
Why is it dependent on repoze.who? A nicely decoupled system would
only need to know that authentication had succeeded which generally is
identifiable by REMOTE_USER being set in the WSGI environment
dictionary passed from outer middleware, where outer middleware has
performed authentication, or even where it didn't and REMOTE_USER was
set by a web server capable of doing authentication itself such as
Apache.
Graham
> * It's not hard to get started!
>
> It's not a stable software yet, but it's just reached its first beta.
>
> Cheers!
> --
> Gustavo Narea <http://gustavonarea.net/>.
>
> Get rid of unethical constraints! Get freedomware:http://www.getgnulinux.org/
>
> signature.asc
> < 1KViewDownload
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
