I'm only guessing, since while I've been around django, sha1 has been used as the passwd hash function.. But could you check that if the password actually fits in the space reserved for in the database? my point is (if there is any;)) that md5 creates a 32 digit hash sum and sha1 creates a 40 digit instead...
Milton Waddams wrote: > On 2/16/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > .... > > Hmmm, I don't recall anybody having this issue, so I suspect it's > > something with your code. Are you, perchance, subclassing the > > auth.User model or doing anything else custom with the auth app? > > Nope, only thing I'm using auth for is for the auto generated admin. > > I have probed a little deeper to find a solution... > > When I change the password using User.set_password() it changes to > sha1 in the database however when I attempt to login through the > administration interface it doesn't authenticate. > User.check_password() returns True when supplied with the correct > password. > > For now I've commented out the lines in check_password which change > the password to sha1 if it isn't sha1 and it appears to be working > fine for me, when I have time I'll look into it in more detail. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
