MySQL users, native vs table

[RopeADope]

Hi all.

 

My end result to my current project is basically a dashboard type deal, PHP driven with a MySQL database.  My question is--"When setting up users to generate info from the database, should these users be established in the MySQL DB, or should they be in a "users table" that PHP checks for authentication?"

 

I realize the question sounds like its asking the same thing twice, but I guess the essence of what I'm getting at is "MySQL.users vs MyDB.users?"

[premiso]

MySQL.Users is for database access. You should only create users in there you want to give access to the database. You will want to setup your own users table for your php script.

[RopeADope]

MySQL.Users is for database access. You should only create users in there you want to give access to the database. You will want to setup your own users table for your php script.

 

The users will have access to the dashboard, as well as be able to enter/update/view data.  So for this purpose, would they need to be in MySQL.users or can I use a generic MySQL.users user with select/update/insert privileges?

[Mchl]

You'll probably be better off creating a users table in MySQL. The reason being, it's easier to create access rules based on application 'actions' a given user can perform instead of giving/forbidding them access to raw MySQL objects.

 

On the other hand, if your application is something like phpMyAdmin, that actually deals with access to MySQL objects, then perhaps using mysql.users IS indeed a better choice.

 

The users will have access to the dashboard, as well as be able to enter/update/view data.  So for this purpose, would they need to be in MySQL.users or can I use a generic MySQL.users user with select/update/insert privileges?

 

[RopeADope]

You'll probably be better off creating a users table in MySQL. The reason being, it's easier to create access rules based on application 'actions' a given user can perform instead of giving/forbidding them access to raw MySQL objects.

 

On the other hand, if your application is something like phpMyAdmin, that actually deals with access to MySQL objects, then perhaps using mysql.users IS indeed a better choice.

 

Ah.  This isn't really a phpMyAdmin type program, its more an interface for viewing and working with data, not actual table structure or anything that in depth.  So my next question would be, can I have 50-100 users connected to the DB with a generic MySQL user at the same time?  For instance, can I have Fred, Ted, and Bob all logged into the dashboard and INSERT/UPDATE/VIEW data with the same MySQL user?

[premiso]

Yes, you can. Because they are logged in on the code side (via php). MySQL sees it all as the database user setup for the account. That is how this site works, and countless others.

[RopeADope]

Yes, you can. Because they are logged in on the code side (via php). MySQL sees it all as the database user setup for the account. That is how this site works, and countless others.

 

Ah, I see.  Thanks for clearing it up!

[Mchl]

In other words: Users are logging into your application. Your application is logging into database