If you select a typical asp.net mvc project, and when you select the authentication type "Individual user accounts", the first registration will create a database with a name like "aspnet-testIdentity-20180628111737.mdf"
Is it possible to use this database for the further work of the application (I understand that it is technically possible, but will it be correct)? How do I properly organize the base when I need to solve for example the following problem:
- authorized users have access to certain methods
- Notifications come to users, I want to store notifications in a database in a table with the following structure: notificationId, notificationText, userId, received. It turns out that when a user accesses, notifications will be read from the database. For the userId field, there must be a foreign key on the Id in the AspNetUsers table
How is it generally correct to build a base for an application in which authorization based on an asp.net identity is assumed?
