if you are using RPX(janrain) you can have both methods at the same login page:
http://web2pyslices.com/main/slices/take_slice/124 -- Bruno Rocha [ About me: http://zerp.ly/rochacbruno ] On Tue, Jun 21, 2011 at 6:36 AM, Carl <m...@carlroach.com> wrote: > after some digging I've found that creating Auth(db) is where the > controller can be set (and is, of course, "default" by default :) > > I'm calling auth=Auth(db) in my db.py file > > Am I heading in the right direction to change the call to Auth() > depending upon if the user is logging in via /init/default/user or > init/id/user ? > Or should I keep each different authentication type in default.py and > "configure" in "some way" ? > > Guidance sort. > > > On Jun 21, 10:01 am, Carl <m...@carlroach.com> wrote: > > My app to date has had one controller, default.py > > > > I had multiple login methods (LinkedIn and email address) for > > different sets of users. > > This caused a problem: when a user wasn't logged in, my app defaulted > > to prompt for a LinkedIn OAuth-style login. > > > > So I decided to pull the code for the two sets of user a part into > > init/default.py and a new file, init/id.py > > > > both now implement their own function user() > > > > Trouble is, when I call init/id/id which are > > decorated:@auth.requires_login() the user() function in init/ > > default.py is called rather than the one in init/id.py > > > > Where am I going wrong? >
