I've been working on a medical record information system for past two years which uses Asp.Net MVC platform and only works with internally defined users. We have our own users definition and this system doesn't interact with any open authentication or external
authentication provider. Consequently, we decided to use Asp.Net Identity framework to implement security for this application. The reason we made this selection was that we assumed it's better to use a Microsoft designed framework for this purpose instead
of implementing security structure on our own effort. (Maybe it gives a better design and form) However, As a software architecture of this project and after two years of working with Asp.Net Identity (we started with version 1, now we are using version 2),
I have a negative feeling about this framework.
First of all, it seems intrinsically this framework has been designed to work with OWIN and Open Authentication. This is an issue for us since we don't need ...
Go to the complete details ...