skoruba/IdentityServer4.Admin

Add option for Admin UI without Asp.Net Core Identity

Open

#501 opened on Feb 16, 2020

View on GitHub
 (4 comments) (5 reactions) (1 assignee)C# (3,486 stars) (1,125 forks)batch import
help wantedpriority: hightask

Description

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 (#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

Contributor guide

Tech stack
csharp
Domain
backendauthentication
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C#ASP.NET CoreIdentityServer4appsettings.json configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the current usage of Asp.Net Core Identity across the Admin UI codebase. Look for references to Identity in startup configuration, seeding mechanisms, and UI components. Review the appsettings.json structure and understand how configuration options are currently implemented. Consider the two approaches mentioned: adding configuration flags or using dotnet new template parameters to conditionally include Identity related code.