one thought: for one set of users I'll have been given an email address and password and for the other set I'll have a LinkedIn user key
On 16 October 2010 06:06, Carl <carl.ro...@gmail.com> wrote: > good question! > > if the account is authenticated using linkedin then I want to set-up the > account a specific way. > > if the account is registered/logged-in the 'usual way' then I want to > set-up the account in a specific but different way. > > I take your point with respect to "trust". I've missed a night's sleep so > will think on that some more. But now I need to go out :) > > > On 16 October 2010 05:50, mdipierro <mdipie...@cs.depaul.edu> wrote: > >> I guess what I do not understand is the following. >> >> You authenticate somebody using linked (or other method), yet how do >> you decide how to setup is account? You cannot decide from the url! No >> because it would not be safe since the user decides the url. >> >> massimo >> >> On Oct 15, 10:59 pm, Carl <carl.ro...@gmail.com> wrote: >> > thanks for the pointer Radomirs. >> > the slice has the registering step disabled >> > >> > rpxAuth.rpx_disabled = ['register','retrieve_password', >> > 'reset_password','change_password','profile'] >> > >> > but doesn't say how to skip registering by the user *and* still perform >> some >> > register actions in the code. The above snippet prevents the user from >> > registering. But how to have one's code, for example, set some >> permissions >> > or set-up the account is some other way. >> > >> > On 16 October 2010 04:48, Radomirs Cirskis <nad2...@gmail.com> wrote: >> > >> > > RPX (LinkedId) + web2py Auth module >> > > this could help:http://www.web2pyslices.com/main/slices/take_slice/28 >> > >> > > Cheers, >> > > rad >> > >> > > On Oct 16, 12:40 pm, Carl Roach <carl.ro...@gmail.com> wrote: >> > > > I've got authentication working with LinkedIn. But no registration >> step >> > > happens... I would like to add a set of permissions the first time a >> new >> > > user logins in via LinkedIn. >> > >> > > > For a second type of user I offer a registration page to get >> > > email/password and then add a different set of permissions. >> > >> > > > So the piece I'm missing is: how do I fire off a registration step >> for my >> > > "LinkedIn" users? >> > >> > > > On 16 Oct 2010, at 00:19, Radomirs Cirskis <r...@nowitworks.eu> >> wrote: >> > >> > > > > Hi Carl! >> > >> > > > > you can implement two registration similar to the technique >> Massimo >> > > > > advised the authentication. >> > > > > You could look into CAS. Not 100% sure, but it could be solution >> for >> > > > > your case. I could be mistaken. Can you elaborate further on what >> you >> > > > > are trying to achieve? >> > > > > rad >> > >> > > > > On Oct 16, 10:00 am, Carl <carl.ro...@gmail.com> wrote: >> > > > >> 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) >> > >> > >> > >
