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
I am wondering how to modify the solution for use case if it is not required to use Asp.Net Core Identity. From my point of view is possible to do these things:
Add some configuration parameters into appsettings.json and hide all functionalities which are related to Asp.Net Core Identity
This use case of excluding of Asp.Net Core Identity requires redesign seeding mechanism for database as well, because it is not necessary to create tables for Identity in case if it is not used.
Feedback for this modification is really welcome. 👍🏼
Thanks
The text was updated successfully, but these errors were encountered:
This would be a great addition! We'd be interested in implementing this Admin UI but only plan on using it for external identity providers, so internal user management is unnecessary for our use case.
We are also looking at using this UI but we only need the IdentityServer. Any update?
I think for most of the people looking for this scenario is because they already have an implementation that they would benefit to add a UI on top of. So I would say, drop the seeding considerations. If anyone needs that (starting from scratch without ASP Identity), they could get the quickstart directly from IdentityServer.
So looking at your backlog I think this one and #55 should be considered under the same scope
I am wondering how to modify the solution for use case if it is not required to use Asp.Net Core Identity. From my point of view is possible to do these things:
Add some configuration parameters into appsettings.json and hide all functionalities which are related to Asp.Net Core Identity
Create some variables which will be used during creation of solution via command -dotnet new template and regarding theses variables all related files will be removed (Add flag for exluding Asp.Net Core Identity from dotnet new template #79)
This use case of excluding of Asp.Net Core Identity requires redesign seeding mechanism for database as well, because it is not necessary to create tables for Identity in case if it is not used.
Feedback for this modification is really welcome. 👍🏼
Thanks
The text was updated successfully, but these errors were encountered: