Open mjrousos opened 2 years ago
We have a couple of requests for this in #261
Would this include consideration around Microsoft.AspNet.Identity (in particular, Microsoft.AspNet.Identity.EntityFramework) as well, or is that a new issue (or even out of scope for this repo)?
Even though EF6 supports .NET Standard 2.1, Microsoft.AspNet.Identity.* doesn't (only .NET 4.5.1), so when the data layers have this dependency (for things like IdentityUser
), business layers are blocked from migrating to .NET Standard 2.0 or higher. Currently the answer here is doing it all in one hit (which is antithetical to incrementally migrating), or duplicating the identity types in the DAL to remove the dependency.
(I'd love to move to EFCore first, but netstandard2.0 hasn't been a supported target since 3.1, and I'd be rewriting UserStore
and such to work with ASP.NET).
Hi, is there any progress on this request? Appears to be no activity since March 2023 and its a pretty crucial piece of the incremental migration story.
Hi Thanks for this amazing work. We are trying to upgrade out 20 year old app and some of our clients use Windows authentication. Is there any progress here or #246 ? Without this we are unable to use Incremental upgrade.
@twsouthwick @adityamandaleeka @mjrousos Any updates/plans on this please
Current tooling allows incremental migration to share ASP.NET authentication with an ASP.NET Core app for quick startup moving endpoints.
In addition to this existing functionality, it would be useful to be able to have the ASP.NET Core authenticate users and forward identity information to the ASP.NET app (in cases where it's necessary to fall back to the ASP.NET app to handle a request). This would allow developers to migrate authentication at any point in the migration process that was convenient instead of having to wait until all ASP.NET endpoints have been migrated first.