I am trying to figure out what would be the best approach on creating SSO in production running system. There is ASP.NET legacy application with DotNetNuke (that's where all identity tables are stored). The requirement is to have in a future more applications shared by the same identity so user wouldn't need to login to each application every time, basically that's what SSO solves. Right now I see these possible solutions:
- Use Duende Server that provides SSO but then I have to make a migrate user identity tables data from DotNetNuke and make a mirror database. What is worse that two database need to be maintained. One database changes have to appear in another database. It's potentially error-prone in a future if data is lost.
- Try to mount SSO on current legacy application. Unfortunately it means SSO will be highly tight with non identity dependencies and I am not sure if DotNetNuke will allow easily extend to SSO.
- Any other solution ?
Other facts to mention: incoming new applications will have subdomains that means it's going to be possible to share the same cookie between the apps.