Re: basic django auth fails on valid user

2010-03-25 Thread Tom Evans
On Thu, Mar 25, 2010 at 2:48 PM, Jim N wrote: > Thanks Tim, > > Yes, I just saw this.  I was subclassing auth.User because I didn't > know the right way to do it. > > Now I am on the right track. > > Just one thing I can't figure out. > > "When a user profile model has been defined and specified i

Re: basic django auth fails on valid user

2010-03-25 Thread Jim N
Thanks Tim, Yes, I just saw this. I was subclassing auth.User because I didn't know the right way to do it. Now I am on the right track. Just one thing I can't figure out. "When a user profile model has been defined and specified in this manner, each User object will have a method -- get_profi

Re: basic django auth fails on valid user

2010-03-24 Thread Tim Shaffer
I think this could all be simplified a bit if you used a UserProfile model instead of subclassing auth.User. http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users Was there a specific reason you were subclassing auth.User? -- You received this message beca

Re: basic django auth fails on valid user

2010-03-24 Thread Jim N
OK, so it seems what's happening is that the password is being stored in `api_qotduser` plain text. I *believe* Django expects a hashed password? More strangeness: I switched to using check_password and NOW Django is querying `api_qotduser`, where before it was querying `auth_user`. New login vi

basic django auth fails on valid user

2010-03-24 Thread Jim N
Hi, I am writing a basic login routine using django users. Here is the view: def login_result(request): username = request.POST['u'] password = request.POST['p'] logging.debug("look for user %s / %s" % (username, password)) user = authenticate(username=username, password=password)