I wrote up a draft of my thoughts on what is needed for TurboGears authentication/authorization: http://trac.turbogears.org/turbogears/ticket/11
Creating a generic, yet simple authentication and authorization framework is not easy, but at the same time there's been enough other work done that our implementation is greatly simplified because other people have already figured out what works well :) The ticket may sound difficult but, for anyone who wants to work on it, feel free to toss out questions here. It need not be that difficult, and MultiAuth may already have most of the work done. (I haven't looked at MultiAuth yet, so I don't know.) Kevin On 10/5/05, Lethalman <[EMAIL PROTECTED]> wrote: > > It's not important for me that you add my auth model, the importance > is that this auth has a purpose in turbogears and it become useful in > projects. > Since i have no experience with CherrPy, conseguently i don't have > practice with its auth methods. However if you think that cherrypy > auth methods are enough then don't care about mine. > > Just give me some hints about this task, from my poor english i > understood this: use my Authentication based on the already existing > cherrypy auth methods. > > I just suggest to use my class as an abstract layer for cherrypy auth, > to let the user have a better interface with the framework. > > -- > www.italianpug.org - Italian Python User Group Founder > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
