If you are ok digging through code, in mostly all of my apps I use a "CustomAuthntication.py" module that is basically a class that mimics web2py's but it is very thin compared to the stock's, I use it this way not because 'mine is better' but because I wanted to control my registration and authentication more closely to my own apps.
If you want, take a look at https://bitbucket.org/speedbird/qastack/src/da67a4653854/modules/CustomAuthentication.py this is qa-stack's authentication core, the "authenticate()" method is really the core and I do use a custom user's table, overall it is not too far from web2py's internal authentication, but just to show how you can implement your own authentication system, controlling every aspect of the user registration/login experience without having to 'reinvent the wheel'. Cheers, Julio On Thursday, February 23, 2012 9:48:49 PM UTC-8, davidkw wrote: > > Thanks, I wasn't trying to do anything specific. I'm just going > through the tutorial and trying to understand how stuff works. > > Thanks for the link though. I hadn't found the settings info before, > and it's very helpful. > > On Feb 24, 12:19 am, Anthony <abasta...@gmail.com> wrote: > > On Thursday, February 23, 2012 11:57:49 PM UTC-5, davidkw wrote: > > > > > Hmm, I'm still having trouble creating separate actions and views for > > > auth. The ones I create don't seem to override the default ones. > > > > > Is there any way I can expose auth as a controller? And rewrite the > > > methods in there? > > > > No need to do that. Show some code and we'll see if we can figure it > out. > > Note, you'll need to change any links to the old URLs to point to your > new > > actions. You also have to set auth.settings.login_url to your new login > > action so Auth knows where to redirect when a login is required. > > Seehttp://web2py.com/books/default/chapter/29/9#Settings-and-messages. > > > > Anthony
