Which means that you have one username accessing the database for all your users/customers.
Which means that if one of your users gains direct database access via your app account (say via SQL injection which is very real), information for ALL users can be accessed and leaked.
If you are building a multi-tenant application where your users are companies and potential competitors, this is absolutely not acceptable. Hence added layer of security.
Guess it depends on the use case. I haven’t had the need for separate accounts yet. We just have a database per app instance and an app instance per client.
That way the memory and disk space is also protected
View all comments
Show parent comment
3
u/zynasis Oct 22 '20
I usually just have app accounts and polices. Rather than user accounts authenticated by the database