Thanks Julio. Given your interest in this perhaps you want to take the job of porting CAS on Auth?
Massimo On Mar 16, 1:45 pm, Speedbird <[email protected]> wrote: > No difference actually (well, Tools is really my "poor's man > authentication on steroids :), bear in mind that my app was coded > where there were still many changes being done to T2 (pre 1.55) and I > was getting a grasp on authentication and authorization, I am > currently developing an app that I can tell you it'll be very useful > for the community and I am precicely using web2py tools (with the > added benefit of the decorators), take the original post in my blog as > a proof-of-concept. Thanks for your hard work Massimo. > > Julio > > On Mar 15, 10:23 pm, mdipierro <[email protected]> wrote: > > > Thank you Julius, > > > Could you explain what are the differences when compared with the new > > default Auth (http://mdp.cti.depaul.edu/examples/default/ > > tools#authentication)? > > > Massimo > > > On Mar 16, 12:18 am, Speedbird <[email protected]> wrote: > > > > Howdy, > > > > I ended up with the same predicament and at the end of the day decided > > > to implement it myself, maybe not the most "desirable" option but it > > > has worked perfectly for me, writing an authentication/authorization > > > pattern is not as hard as you would imagine, especially in web2py, I > > > wrote a bit about it in my (web2py-based :) > > > blog:http://www.julioflores.com/zblog/blog/view/9-Theonly issue I see > > > with this approach would be scalability. Cheers. > > > > -jf/sb > > > > On Mar 14, 10:38 am, David Marko <[email protected]> wrote: > > > > > Is there anyone who used CAS (https://mdp.cti.depaul.edu/cas) with the > > > > new Auth system built-in in web2py? We have to create a several > > > > appliances with a shared authentication system and we are considering > > > > the right way. > > > > > Is there any 'good practice' for following scenario? For one client > > > > we need to develop several apps(project management, incoming invoices > > > > managment, outgoing invoices managment etc.) Though these apps must > > > > work separately(at least are developed separately), they must share > > > > some common parts, like shared options, authentication (where roles > > > > specify, which app is availabe for which user etc. ) Overall its very > > > > common scenario, when you have many smaller customers each having many > > > > apps, rather than developing one big application shared for all. > > > > > You experince is appreciated! > > > > David- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
