Embedding an asp.net identifier in an existing entity infrastructure database

I am trying to update an old website. It already has an existing database with a user and a role table with the data existing in it.

I need to create a new web api and a new web project and integrate the ASP.NET identifier into an existing database.

I have currently set up my project breakdown solution as follows:

  • Domain
  • Services
  • WEB_API
  • WEB_UI

My goal is to implement Identity at the service level so that both WebAPI and MVC sites can use the same authentication mechanism.

At the moment I'm pretty overloaded, I read a lot of textbooks and articles in the last day or two and got options for reintroducing IUserStoreand IRoleStore. As well as displaying various objects in OnModelCreatingMethod.

I can’t find a tutorial that focuses on what I want to do. My database is different than just reassigning column names. And I don't want to reimplement entire Identity stores, as there are only a few conflicting fields. Most of the links I found are related to using mysql instead of EF. I still want to use the Entity Framework.

The problems that I have are:

  • The current user table in the database uses Intpk, notGUID
  • Password Hashing. , Identity .
  • User Identity , , .
  • Database First, .

, , : , . ? , ?

. , ApplicationUser. , , , .

+4
1

- , , BACK-UP !

.

, , , , , , " Visual Studio 2013". http://www.asp.net/identity/overview/migrations/migrating-an-existing-website-from-sql-membership-to-aspnet-identity

, .

Nuget:   Microsoft.AspNet.Identity.EntityFramework,   Microsoft.AspNet.Identity.Owin,   Microsoft.Owin.Host.SystemWeb

- script, : https://aspnet.codeplex.com/SourceControl/latest#Samples/Identity/SQLMembership-Identity-OWIN/Migrations.sql

POCO, .

( . .)

+3

All Articles