Creating own Register/users Table instead of migration Identity

osyris 236

While creating a register system I was thinking to creating my own tables:

UserTable = email, encrypted password ,name etc.
RoleTalbe = roleName and RoleDescription
RoleUserTable = user and RoleName.

It seems to me better instead of having to migrate 8 tables were i would only use 3 of them.

Is creating your own tables an good option do some people or companys do this?
or is this something that is absolutly not done.

AgaveJoe 26,191 Reputation points

2021-07-09T18:26:53.973+00:00

Identity is an API and data store not strictly a database.

The proposed design has redundant data (not normalized), password should be hashed not encrypted, and it does not take advantage of claims. In this case, I recommend implementing Identity because it is more secure and modern than the proposed design.

The data store a company uses is too open of a question to answer. For example, a company might use Azure AD. The same company might have an older Intranet app that uses Windows Authentication. It is not uncommon to find legacy apps that have proprietary security and data stores.