Migrating from DotNetNuke to ASP.NET Core
I have a DNN based application (bunch of DNN modules) and would like to gradually migrate this application to plain ASP.NET Core. (get away from DNN) I am only dependent on DNN control and navigation, everyone else is mostly simple ASP.NET Web Forms. (or better: web user controls in DNN)
The plan is to create a completely new application (different subdomain) and be the first to migrate my user management to .NET Core Identity. Users must sign in through the new app and must switch between Core App and DNN during the migration period. I want to use a new identity based mechanism and will need to keep users in sync with the DNN membership based tables until I can drop the last DNN module.
From: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity Identity seems to create its own cookie which is completely different from DNN. Does anyone know a way to create a generic cookie that will allow users to navigate from the old to the new application without having to log in twice? Or is there a better way to implement this functionality?
UPDATE: Doing more research and at the moment it seems more appropriate to split this project into two phases: 1. Start a new application with MVC 5 (for stability) 2. Migrate MVC 5 application to .NET Core after a while
The question still remains for MVC 5 using OWIN authentication in this case. Is it possible to create a shared authentication cookie between MVC and DNN?
source to share
For those with the same problem, I found out that what I want to do is not possible. The authentication cookie format has been changed using OWIN and is not backward compatible with the previous version of FormsAuthentication.
I was able to create an OWIN cookie with the same name, MachineKey encryption, etc., but the content is different and DNN doesn't recognize this.
I will have to add an extra phase to my migration. 1. Create a new application with MVC 5, but use the old authentication 2. After migrating all modules, I can migrate to OWIN 3. Migrating to ASP.NET core
source to share