thanks for your reply, shawn. that's a good idea, and i already have a one-to-one table inherited from User where i can stash the initial encrypted password. the only thing i don't like about doing it this way is that i am currently trying to use as much generic, built-in django as i can and that means in this case that i am using the standard django login function (i.e. (r'^accounts/login/$', 'django.contrib.auth.views.login')).
i first thought that i might be able to just write a little wrapper around that function to implement the logic you suggested, letting the generic function log the user in and then deciding where to redirect based on the password comparison between User and the one-to-one table. but django.contrib.auth.views.login has a redirect buried right inside it, so i don't see how i can do this without re-implementing the whole login function in my project. that's not a big deal from a code standpoint; just a copy-paste and adding the additional logic which is minimal. but i was hoping to avoid replacing the generic django functionality in areas like this where future django updates might cause conflicts. this might not be a big deal in this case, but i am relatively new to django and don't have a sense of where this kind of hacking is safe and where not. On Jul 17, 10:35 pm, Shawn Milochik wrote: > This isn't ideal, but it should work (or prompt someone to propose > something better). > > Add a one-to-one table for the user, with a field containing the > initial password (encrypted, of course, so it looks like the password > in the auth_user table). > > When the user logs in, have the login page check to see if the > passwords match. If they do, redirect to the password change page > instead of the normal redirect page. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
