On Feb 14, 7:11 pm, Gustavo Narea <[email protected]> wrote: > Hello, Michael. > > TurboGears' "identity" doesn't exist anymore as of v2; instead repoze.who and > repoze.what is used for authentication/identification and authorization, > respectively. Please read the > documentation:http://turbogears.org/2.0/docs/main/Auth/index.html > > What you describe is just the way repoze.who is configured by default, but > it's absolutely pluggable and extensible. If you want to go beyond what is > currently explained in the documentation on authentication with repoze.who in > the TG2 docs, then you want to visit the repoze.who's > manual:http://static.repoze.org/whodocs/ > > HTH. > > - Gustavo. > > On Saturday February 14, 2009 16:01:50 Michel Albert wrote: > > > I am aware that REST has come up quite often already on this list, but > > all current posts seem to miss out on one point: Authentication and > > Authorisation. Now, this is already quite (IMO) excellently using the > > Turbogears identity framework. Would it not be nice to be able to use > > this with RESTful services as well? > > > I just started exposing specific resource of my application using a > > REST filter for cherrypy. But I need auth&auth. GETing the resources > > wont require auth&auth, put POSTing, PUTing and DELETEing would > > require it. However, turbogears identity will show a HTML based login- > > form instead of using HTTP auth. This violates the REST princible and > > is net really usable. > > > To solve this problem until I filnd a better solution I also used a > > cherrypy filter to do auth. I attached the auth and rest filters to a > > sub-controller (http://my_domain/rest) which contains one more > > controller for each resources. It's not perfect, URL-wise, but it's > > working. > > > Is there any work going on to get REST working in a similar manner > > (with auth&auth using tg.identity)? Or am I on my own here? Having the > > cherrypy filters at hand is an extremey powerful tool, but..... is > > there a way to - maybe - detect any identity decorators that may have > > been "wrapped" around a controller method from *whithin* the filter? > > Essentially using the available TG-framework boilerplate to roll my > > own cherrypy filter to do rest with auth&auth? > > -- > Gustavo Narea <http://gustavonarea.net/>. > > Get rid of unethical constraints! Get freedomware:http://www.getgnulinux.org/
Thanks, this sounds interesting. However, my current app is running on TG1.0, so as I can see the "best" method would be to migrate towards TG2.0. But then, how does the roadmap look for TG2. Can it be considered stable enough for production use? As far I can see from the different posts on the web it's pretty much done, and a final release is imminent. Right? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
