A
Anonymous
Guest
Pardon my newbie-ness, my colleague and I are trying to create an asset tracking app for our company. I'm looking for examples of setting up the login screen. Nearly every tutorial I find is the same: They create a database in MySQL, create a users table in MySQL, use the MySQL root account to connect to the DB, compare the username/password entered in the text boxes to the username/password in the newly created users table. Then any further transactions are all completed by the root account (or some other account they designate).
Fine if they want to do it that way, but I don't like that. Instead of creating a user table and adding users to it by their own registration, only a limited number of people will be using this app. We have already created their accounts at the DBMS level, so their accounts are in the mysql.user table. The proper permissions of the tables in our app have been granted to those users. I would like our login form to work so that the username/password entered in the textboxes will attempt to connect to MySQL. If an account has already been created for them in MySql, then they will be free to use the app. Any transactions will not be done through a single account, they will be done by the actual MySql user account of the person being logged in. Is this way just not a good best practice? Just asking because I can't seem to find any examples of it being done this way.
Fine if they want to do it that way, but I don't like that. Instead of creating a user table and adding users to it by their own registration, only a limited number of people will be using this app. We have already created their accounts at the DBMS level, so their accounts are in the mysql.user table. The proper permissions of the tables in our app have been granted to those users. I would like our login form to work so that the username/password entered in the textboxes will attempt to connect to MySQL. If an account has already been created for them in MySql, then they will be free to use the app. Any transactions will not be done through a single account, they will be done by the actual MySql user account of the person being logged in. Is this way just not a good best practice? Just asking because I can't seem to find any examples of it being done this way.