How to implement MVC5 ASP.NET generated identity code into an existing database

Question

0.00/5 (No votes)

See more:

As the title says, I created a new MVC project with visual c# and authentication. Then I've implemented the desired models (and created the database with code first entity framework). What I want to do now is add to that database the intelligence of the authentication that was created by visual studio and addapt it to map my entities.
For instance, I've got a table called Clients. I want that each client have it's own login and permissions. How can I do that?
Thanks

Posted 1-Jun-15 6:28am

Member 11733471

Updated 1-Jun-15 6:31am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Afzaal Ahmad Zeeshan · Accepted Answer · 2015-06-01T06:40:00

Entity framework is based on DML stuff (data manipulation), so using it for CRUD operations won't be a bad idea. But creating a login system on the top of it, would not be a good idea. You would have to create a lot of modules and other stuff. So, don't!

Instead of this, you can use ASP.NET Identity[^]. Identity has a lot of good features, and allows you to take controls of everything (yes, everything) that goes on under the hood. You can use the API to create your own services and use them in your application, change how the Identity system works, add more packages to it and so on.

So, instead of using Entity framework for user logins and permissions (groups or roles, right?) you should use ASP.NET Identity.