We're currently using ASP.NET Identity for handling external user accounts based on the integration explained in this blog post, http://sveinaandahl.blogspot.se/2015/08/how-to-integrate-aspnet-identity-with.html. This was implemented before Episerver had official support for ASP.NET Identity. In this solution it works fine to have external accounts handled by ASP.NET Identity and still use Windows accounts to login to edit/admin-mode.
We're trying now to migrate to Episerver's ASP.NET identity solution but are having problems understanding how to use ASP.NET Identity for external accounts and use Windows accounts for edit and admin mode. We're aware of the recommendation of having separate servers/url for the public web and the edit/admin-mode but in this case the editors use the same url as the public web to login to edit-mode.
Does anyone have any knowledge about how to make this work?
I would recommend a Federated security approach since that handles multiple catalogs so much nicer. Could that be an option in the migration work?