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
Possible way of setting this up, is the creation of a new package Piranha.AspNetCore.Identity.EntityFrameworkCore that provides the EF implementations of IRoleStore and IUserStore. And remove any dependency on Microsoft.EntityFrameworkCore from the Piranha.AspNetCore.Identity package?
As an additional bonus, we can include a file based IRoleStore and IUserStore implementation to the Piranha.AspNetCore.SimpleSecurity package for demo/testing setups.
I would be very happy to further investigate this and submit a PR if this issue and described approach is okay for you guys.
The text was updated successfully, but these errors were encountered:
See for ref:
At the moment, the
Piranha.AspNetCore.Identity
package has a dependency onMicrosoft.EntityFrameworkCore
:piranha.core/identity/Piranha.AspNetCore.Identity/IDb.cs
Line 15 in fe7fd28
But what if one does not want to store user and role data in a relational database? Like in my customer's case, we would like to reuse the existing user and role management and UI/Razor features (https://github.com/PiranhaCMS/piranha.core/tree/master/identity/Piranha.AspNetCore.Identity/Areas/Manager/Views), but bring our own custom Identity storage provider.
Possible way of setting this up, is the creation of a new package
Piranha.AspNetCore.Identity.EntityFrameworkCore
that provides the EF implementations ofIRoleStore
andIUserStore
. And remove any dependency onMicrosoft.EntityFrameworkCore
from thePiranha.AspNetCore.Identity
package?As an additional bonus, we can include a file based
IRoleStore
andIUserStore
implementation to thePiranha.AspNetCore.SimpleSecurity
package for demo/testing setups.I would be very happy to further investigate this and submit a PR if this issue and described approach is okay for you guys.
The text was updated successfully, but these errors were encountered: