thanks M.
adding to def candidate()
auth.auth_user = 'candidate'
has that side sorted.
for my function agent() the process is a little more complicated.
While Candidates have to "formally" register first and then login agents can
be "automatically" registered (I need to add some permissions and do other
one-off stuff) when they come back from LinkedIn.
The problem is that registration doesn't take place at all and I can't
figure out how to get this one-off registration phase called. can you point
me in the right direction?
On 15 October 2010 19:22, Carl <carl.ro...@gmail.com> wrote:
> I'm glad I don't need two user tables. I ideally would want to stick to a
> single table.
>
>
>
> On 15 October 2010 19:14, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
>> Not necessarily and I would not do it that way but you can.
>>
>>
>>
>> On Oct 15, 1:12 pm, Carl <carl.ro...@gmail.com> wrote:
>> > thanks M.
>> >
>> > Do I understand that your solution is to have two separate user tables
>> in
>> > db.py?
>> >
>> > On 15 October 2010 18:42, mdipierro <mdipie...@cs.depaul.edu> wrote:
>> >
>> > > look into default. You can replace
>> >
>> > > def user(): return dict(form=auth())
>> >
>> > > with
>> >
>> > > def agent(): return dict(form=auth())
>> > > def candidate(): return dict(form=auth())
>> >
>> > > and in the two functions you can set different default for auth_user
>> > > fields.
>> >
>> > > On Oct 15, 8:45 am, Carl <carl.ro...@gmail.com> wrote:
>> > > > Is there a way to use [app]/default/agent instead of
>> app/default/user?
>> >
>> > > > I want to have two implementations of authentication (/agent and /
>> > > > candidate)
>> >
>> >
>>
>
>
