You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code of ASP.NET Identity is using the domain object CoreWikiUser directly. There is also no abstraction of the Identity code, making it impossible to refactor it out to the Application layer.
The issue has been raised before in the Identity repo: aspnet/Identity#883
As that issue states it has been fixed, maybe we need to look what consequences that has for our code and how we can improve it to achieve that separation.
The documentation can help there as well as it show how to create a IUserStore: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity-custom-storage-providers?view=aspnetcore-2.1
That takes at least the EF out of the equation. UserManager is going to be trickier, not sure yet whether that is needed. It depends on whether the session lives at the front-end or the back-end. If it's front-end only, then the mobile/API back-end (once created) might need its own depending on the functionality being exposed.
The text was updated successfully, but these errors were encountered:
The code of ASP.NET Identity is using the domain object CoreWikiUser directly. There is also no abstraction of the Identity code, making it impossible to refactor it out to the Application layer.
The issue has been raised before in the Identity repo: aspnet/Identity#883
As that issue states it has been fixed, maybe we need to look what consequences that has for our code and how we can improve it to achieve that separation.
The documentation can help there as well as it show how to create a IUserStore: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity-custom-storage-providers?view=aspnetcore-2.1
That takes at least the EF out of the equation. UserManager is going to be trickier, not sure yet whether that is needed. It depends on whether the session lives at the front-end or the back-end. If it's front-end only, then the mobile/API back-end (once created) might need its own depending on the functionality being exposed.
The text was updated successfully, but these errors were encountered: