On Aug 27, 1:51 pm, Gustavo Narea <[EMAIL PROTECTED]> wrote:
> Hello, everyone.
>
> I'm afraid tg.ext.repoze.who only supports the repoze.who SQL/form plugin(s),
> and thus I'd like to know if we can make it support more so-called identifier,
> metadata and authentifier plugins under the same API? Better yet, why not
> support all of the repoze.who plugins? This would make TG both scale up and
> scale down in authentication.
I haven't had any problems with writing custom repoze.who plugins and
then using them in my TurboGears projects. All you have to do to
disable the sqlalchemy backend is set base_config.auth_backend to
something other than 'sqlalchemy'. The authorize.require decorator
works as well. I haven't updated from the alpha 1 release yet (don't
hit me please), but really I had absolutely no trouble getting my
custom repoze.who plugins working with TurboGears. I pasted this in
one of the other repoze.who threads, and it's horribly outdated, but
I'll paste it again for reference:
http://paste.turbogears.org/paste/3287
Am I missing something that's going on behind the scenes, or did
something change dramatically in the last month? I apologize in
advance if I have, I haven't been watching the trunk closely.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" 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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
