Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I work with a few applications at the company I work for. I would like to know what should be a better choice:
What do you think will be the advantages or drawbacks?
I would go with a user per application. If your company is of any size, you will quickly find yourself spending all your time creating and destroying MySQL users.
It is better to maintain the user logins in a database for authentication on application startup, and then the application it’s own connection/user to MySQL (which it also uses to authenticate the user).
Then limit all your security based on the user rights that you design in your user table, instead of relying on MySQL to keep people in check.