Re: Adding Users

["Aaron D. Turner" <aturner@best.com>]

-----BEGIN PGP SIGNED MESSAGE-----


We should make random generated passwords that are then emailed to the
person.  This allows us to verify the persons email address was not a
fake or mistyped.  After they recieve the email they can login and do
stuff.


- -- 
Aaron Turner           | Either which way, one half dozen or another. 
aturner@pobox.com      | Check out the Red Hat Linux User's FAQ Online!
www.pobox.com/~aturner | http://www.pobox.com/~aturner/RedHat-FAQ/
All emails from this account are PGP signed.  Lack of a signature is "bad".
PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80  59 6E 60 BF 45 1B 20 E8


On Mon, 8 Feb 1999, Micah Yoder wrote:

> OK, just some ramblings about the process of adding a user.
> 
> I think I'll do this in PHP, as I already wrote PHP code to add users to
> another system, and I think this will be somewhat similar.
> 
> The PHP program, when run without any POST form data, simply displays a
> form for all the relevant information.  When it is submitted, the same
> script runs again and checks all the entries.  Entries that are OK are
> echoed back, and entries that are bad produce HTML text boxes to fix
> them.
> 
> Here's what I suppose we'll need, and the required checks:
> 
> First Name - check that it's not blank
> Last Name - same
> MI - probably no check here.  Not everyone has MI, and its not really
> necessary anyway.  Do we even need it in the DB?
> Handle:  No check
> Description - is this for US to fill out or should it be on the form?
> E-Mail - check that it has an @ and a . in that order (I guess...)
> Fake E-mail - no check
> Password - Check that it exists.  How strict should we be on making it a
> good password?  Should we run it through a checker program that makes
> sure it's not in the dictionary and is at least 5 characters?
> Cookies - checkbox yes/no, no check needed
> URL - no check
> 
> I assume the following would be set to defaults by the script:
> 
> UserID (auto-increment in Db)
> RoleID (role with least priveleges)
> QperDay - what's this for exactly?
> InceptTime (Current date/time)
> ModTime (same)
> TTL (null???)
> 
> We'd then have another form to modify all that, and would only be
> accessible to us.  Actually it would be the same PHP program that
> allows the user to modify his/her record, but it would only display
> general info if an administrator didn't run it.
> 
> Any more ideas?
> 


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNr9hRjM3jpXy1kJtAQGYTgP/VwATEO0IFql+T0WIfC8C2dki1rBHUmQK
+9rhe1PjbbZEwkMex8olCSF+USwmbsumA7Ey0b81ZM6eAd/A4hMOuoZtgW6UQB1R
a6ayCGk6oXBdanV0k+WKy4xHJ7m/z/tmEjBFyIRKWRJ9AwboiBrYt+7CdqmmKlLy
maCxRYCVFcA=
=v0Ld
-----END PGP SIGNATURE-----