I solved partially the issue by properly using the following values in the development.ini file:
authkit.setup.method = form, cookie authkit.form.authenticate.user.type = mainapp.accounts.model:UserManager Note that this affect the login view by replacing the old one with a custom form which look poor but seem to allow login correctly using auth_tkt (feature) and cookie auth. Note 2: the old method (redirect) seem broken as a result and returns a looping 302 response code when attempting to access the original login view/form. Not sure how to solve this. Regards, Etienne On Thursday, 17 April 2014 17:58:37 UTC-4, Etienne Robillard wrote: > > The author has been contacted but doesn't actively support > issues for AuthKit, so sad :-) > > > On Thu, 17 Apr 2014 10:34:49 -0700 > Mike Orr <[email protected]> wrote: > > > You can try AuthKit's author, James Gardner <[email protected]>. > > > > I was going to cc this but the problem description has been chopped > > off in the replies, so I'll let you write it. > > > > > > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
