On Fri, 2007-19-10 at 14:58 +0100, Paul Johnston wrote: > Hi, > > What do we gain from moving to authkit for tg2 over the > existing > identity framework? > > From a user's point of view, OpenID is the main thing. > > From a TG development point of view, we gain not having to maintain > our own authentication system. > > > What do we lose? > > This is unclear at the moment. People have outlined a few things you > can't do (like checking if a user is in any one of a list of groups), > but they seem like pretty rare cases. > > > can anyone comment on > how hard it would be to glue them together, how one might do > so, and > whether that sounds like a good idea or a big can of worms? > > > Probably a bigger can of worms than you want to take on right now. > > You'd want to install AuthKit as WSGI middleware, between the CP WSGI > server and the CP WSGI application. This would mean tampering with > SimpleWSGIServer in turbogears.startup. This might just work (great!) > or you might need all sorts of other tweaks.
Thanks Paul, that's the sort of warning I was looking for. I think I'll continue with the existing identity for the next couple of projects and look into authkit once I've had some time to muck around with WSGI more. Do you think working through the pylons tutorials is the best way to do that or is there a different way of learning it that would be more gears specific? Thanks iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
