W
Wm. Scott Miller
Hello all:
I'd like some advice on the best way to validate and confirm an e-mail
address entered during a registration process. What we are thinking of is
something like the following:
1. User comes to our web site and validates themselves as a member of our
database.
2. User creates a user name and password to be used to log in to our site.
3. User is required to enter a valid e-mail address to finalize
registration.
4. Registration process is suspended until...
5. Server sends e-mail to supplied e-mail address with a link in it that
the user must click on to continue the registration process.
6. User clicks on link and is taken to a log-in page where they will enter
the information supplied in #2
7. Once they have successfully logged in (which also confirms either e-mail
address), they are fully registered and ready to go.
Reason we decided on the above is because of:
1. If e-mail were to be intercepted (either maliciously or by typo by
user), no one but the registering user could confirm e-mail because they
must login with link to confirm e-mail.
2. We need an e-mail in case the user forgets their password so it must be
active and valid for use.
Is there any security holes in the plan?
Additionally, has someone done something like this and have code and/or
suggestions from your experience?
Thanks for all the help,
Scott
I'd like some advice on the best way to validate and confirm an e-mail
address entered during a registration process. What we are thinking of is
something like the following:
1. User comes to our web site and validates themselves as a member of our
database.
2. User creates a user name and password to be used to log in to our site.
3. User is required to enter a valid e-mail address to finalize
registration.
4. Registration process is suspended until...
5. Server sends e-mail to supplied e-mail address with a link in it that
the user must click on to continue the registration process.
6. User clicks on link and is taken to a log-in page where they will enter
the information supplied in #2
7. Once they have successfully logged in (which also confirms either e-mail
address), they are fully registered and ready to go.
Reason we decided on the above is because of:
1. If e-mail were to be intercepted (either maliciously or by typo by
user), no one but the registering user could confirm e-mail because they
must login with link to confirm e-mail.
2. We need an e-mail in case the user forgets their password so it must be
active and valid for use.
Is there any security holes in the plan?
Additionally, has someone done something like this and have code and/or
suggestions from your experience?
Thanks for all the help,
Scott