adding a client name to the login process might make that easier
and it forces a sort of 2 factor authentication making the database 'hopefully'
harder to crack
bastien> From: [EMAIL PROTECTED]> To: php-general@lists.php.net> Date: Tue, 27
Nov 2007 15:30:32 -0500> Subject: [PHP] Question about authenticating
people...> > The subject might be a little misleading... But I couldn't think
of > how better to describe it in a small sentence :)> > What I'm wondering is,
I have a program that accesses a database and > displays the info in that
database... I know, nothing revolutionary > about it... I plan on setting up a
database per customer who uses my > system, and what I would like to do is have
everyone go to the same > address to login... Such as:> > raoset.com/oldb/ they
enter their username/password and get redirected > to their site... Or at least
pull up their database...> > Now that I'm typing this out, I may have thought
of away to do this...> > Set the main page, so that when you login, it accesses
a master > database, which has the username, password, and database name stored
> in it. Write the database name to a session variable, which I could > then
use in my mysql connect file for the database....> > Does that make sense?
Thoughts? Problems? RTFM's? :)> > > --> > Jason Pruim> Raoset Inc.> Technology
Manager> MQC Specialist> 3251 132nd ave> Holland, MI, 49424> www.raoset.com>
[EMAIL PROTECTED]> > -- > PHP General Mailing List (http://www.php.net/)> To
unsubscribe, visit: http://www.php.net/unsub.php>
_________________________________________________________________
Express yourself with free Messenger emoticons. Get them today!
http://www.freemessengeremoticons.ca/?icid=EMENCA122
