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 [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?hl=en -~----------~----~----~----~------~----~------~--~---
