Posted on: 4/14/2015 7:41:50 PM | Views : 936

Hey all,  It's been a while since I've done any serious work using ASP.NET authentication and I'm a bit rusty. Especially now that ASP.NET Identity is the in thing. I'm hoping I can explain what I'm doing and have someone tell me why and where my assumptions are wrong or if they're not wrong.  The application I'm building is going to be HIPAA compliant, and as such I cannot store any personally identifiable information in the database. So I spent some time looking at how ASP.NET Identity works, noting things like my ApplicationUser (which inherits from IdentityUser), as well as the ApplicationDbContext (inheriting from IdentityDbContext). I read a couple MSDN articles and so forth.  I then noticed that IdentityDbContext seems to be tied to the AspNetUsers table in the database. I then noticed something concerning for me in the AspNetUsers table since I'm writing an application which cannot store anything personally identifiable: ...

Go to the complete details ...