- Messages
- 4,148
- Reaction score
- 5
- Points
- 38
I have created a login/authentication system as mention in on of my earlier posts.
The system grants privileges to the users on the db according to a table that contains the privileges to be granted in the rows and the columns hold the tables that they should be granted on. So far I have created a user that I call guest that has "SELECT" granted to this table. So there should be no need for any admin password being passed around. I know that this isn't ideal when there are alot of users as now the script has to check the permissions for that user, icreasing the time it takes to finish the script(fractional difference). When the user signs up they get qued and a cron script creates the account and logs all the nitty grittys in the db.
What I would like to know is :
Is this advisable, what downfalls can I expect ?
The system grants privileges to the users on the db according to a table that contains the privileges to be granted in the rows and the columns hold the tables that they should be granted on. So far I have created a user that I call guest that has "SELECT" granted to this table. So there should be no need for any admin password being passed around. I know that this isn't ideal when there are alot of users as now the script has to check the permissions for that user, icreasing the time it takes to finish the script(fractional difference). When the user signs up they get qued and a cron script creates the account and logs all the nitty grittys in the db.
What I would like to know is :
Is this advisable, what downfalls can I expect ?