Using Asp.net mvc identity in multiple projects

\n If we want to register a user in one of the layers ( not website ) how\n we can do it according to asp.net identity\n\n\nYou do not want bring ASP.Net Identity into Business Logic Layer. It should be at Presentation Layer only. \n\n\n (my first idea is add a user to database and use PasswordHasher Class\n of Microsoft.AspNet.Identity to hash a password , is there a better\n way ? for example move asp.net identity into a new class library\n project or any other ways )\n\n\nFirst of all, if you want to use ASP.Net Identity, you do not want to change or modify its tables. \n\nEasiest way is let ASP.Net Identity create tables first. Then you create your tables such as Customer, Employee. If you need relationship to UserId, use AspNetUsers - Id column as Primary Key or Foreign Key in your tables. \n\nAdam Freeman has free chapter for ASP.Net Identity here.\n\nOther Thoughts\n\nIf you want to change a lot, you might just want to consider using just OwinContext and AuthenticationManager instead of entire Identity. ",