(a) Their user name or ID
(b) A timestamp at which the URL expires
(c) A hash code based off their user name and/or password hash, the timestamp, and some internal site key
All you need for this is your standard database module and Digest::MD5.
Asim: I don't really see how making a separate table for just the authentication process is going to help much. Nobody's going to bother trying to brute-force an MD5 key, and if they're just spamming your site to shut it down (or because they're an automatic script), they're almost certainly going to spam the user signup rather than the user authentication. Either everything should be in one table for the sake of simplicity (and records accessed by ID) or the entire registration record should be in the temp table, and only moved to the primary table once it's been activated.
In reply to Re: Easy Account Email Verification
by TedPride
in thread Easy Account Email Verification
by debiandude
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |