that makes sense to me. still, I have 2 more questions: 1. what kind of query do you use for email confirmation (how do you generate it)? anything special to consider here? I did use a combination of a password-hash with the date_joined so far, but I´m not sure that´s the right way to go. 2. I guess you use a random password first and then override that password, right?
thanks, patrick Am 19.07.2006 um 07:20 schrieb Ian Holsman: > I do something similar to Kenneth. > > the other approach is to use something like OpenID, and make it > somebody else's problem. > > On 19/07/2006, at 3:16 PM, Kenneth Gonsalves wrote: > >> >> >> On 18-Jul-06, at 9:20 PM, va:patrick.kranzlmueller wrote: >> >>> >>> next problem with my user registration process: >>> how do I send the password to registered users after they confirmed >>> their registration? >>> >>> the process should look like this: >>> 1. registration >>> 2. email confirmation >>> 3. account activation & email with username and password >>> 4. now the user can log in >>> >>> since the password is stored encrypted, I´m not sure how to send it. >> >> why send it? What i do is, take the username and email address on >> registration. Then the user gets an email to confirm, the >> confirmation screen also requires him to add password and allows him >> to add other information also. So the password never gets mailed. >> Password reset on lost password is done the same way >> >> -- >> >> regards >> kg >> http://lawgon.livejournal.com >> http://avsap.org.in >> >> >> >> >> >> --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
