Thanks Massimo, thanks Yannick sorry, it was my fault. What i'm talking about is authentication, not authorisation. Perhaps it was little bit late last night... So, my current user.table has user.login_name and user.password (among others). As far as i can see, web2py's auth.module uses email and password for the login process. If possible, i don't want to confrontate my current users with a new login scheme/procedure.So my question is, can this be easily done? Greetings, Paul (captainy)
On 26 Mai, 03:58, mdipierro <mdipie...@cs.depaul.edu> wrote: > I think you need to tell us more about the current process and whether > you want to keep the process, the data, and/or the current > implementation of the process. > > Massimo > > On May 25, 6:20 pm, captainy <weihra...@envi-gmbh.de> wrote: > > > After "playing" a while with web2py, i think i've found a very > > interesting platform for solid and rapid web applications. But i have > > to > > port existing applications to web2py. I want to keep the authorisation > > process for the users of these applications, wich is done by: > > Login: XXXXXX > > Password: YYYYY > > Is ist possible to do it this way in web2py or do i've to rewrite the > > gluon.tools module? > > > Thanks for any help --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
