I am trying to design a system with the below features, and am currently trying to figure out best way to handle Identity :
- There will be multiple decoupled parts of the system, with same customers accessing various parts
- I would like users organized by organizations/companies, i.e. user1 & user2 belong to ORG1
- I would like additional info to be stored within a user profile, info will originate from various systems, as well as global info such as address, etc
- For roles I haven't yet decided whether or not they will be handled by individual apps or globally and specialized in certain apps
My conundrum is whether to use the new MVC Identity released in ASP.NET Beta currently out, or use WIF or Active Directory. I am assuming that a centralized application handling users & their associated admin tasks and then federating to other applications is best. If I understand correctly any of the 3 are able to do that.
What I am wondering is which to use to be most flexible. Basically something that can be expanded later and doesn't have a huge learning curve, possibly to mobile & api use. I don't know enough about WIF or AD as I have never really used them, and ASP.NET Identity is still in beta and not really 100% documented. My experience with authentication systems is working with ones out of the box. I've never really had to deal with SSO or federation
One thing I wanted to add is there is no need for outside registration. Registration will be handled purely by admins, not sure if this ties in at all, but thought it may be of importance