Skoruba.IdentityServer4.Admin

The administration of the IdentityServer4 and Asp.Net Core Identity

Project Status

This is currently in beta version

The application is written in the Asp.Net Core MVC - using .NET Core 2.2

NOTE: Works only with IdentityServer4 version 2.3.0 and higher 🚀

Requirements

Install the latest .NET Core 2.x SDK (using older versions may lead to 502.5 errors when hosted on IIS or application exiting immediately after starting when self-hosted)

Installation via dotnet new template

Install the dotnet new template:

dotnet new -i Skoruba.IdentityServer4.Admin.Templates::1.0.0-beta6

Create new project:

dotnet new skoruba.is4admin --name MyProject --title MyProject --adminrole MyRole --adminclientid MyClientId --adminclientsecret MyClientSecret

Project template options:

--name: [string value] for project name
--title: [string value] for title and footer of the administration in UI
--adminrole: [string value] for name of admin role, that is used to authorize the administration
--adminclientid: [string value] for client name, that is used in the IdentityServer4 configuration for admin client
--adminclientsecret: [string value] for client secret, that is used in the IdentityServer4 configuration for admin client

How to configure the Administration - IdentityServer4 and Asp.Net Core Identity

Follow these steps for setup project to use existing IdentityServer4 and Asp.Net Core Identity

Template uses following list of nuget packages

Available nuget packages

Running in Visual Studio

Set Startup projects:
- Skoruba.IdentityServer4.Admin
- Skoruba.IdentityServer4.STS.Identity

Configuration of Administration for Deployment

Administration UI preview

This administration uses bootstrap 4
Admin UI

Security token service (STS)

Forms:

Cloning

git clone https://github.com/skoruba/IdentityServer4.Admin

Installation of the Client Libraries

cd src/Skoruba.IdentityServer4.Admin
npm install

cd src/Skoruba.IdentityServer4.STS.Identity
npm install

Bundling and Minification

The following Gulp commands are available:

gulp fonts - copy fonts to the dist folder
gulp styles - minify CSS, compile SASS to CSS
gulp scripts - bundle and minify JS
gulp clean - remove the dist folder
gulp build - run the styles and scripts tasks

EF Core & Data Access

The solution uses these DbContexts:
- AdminIdentityDbContext: for Asp.Net Core Identity
- AdminLogDbContext: for logging
- IdentityServerConfigurationDbContext: for IdentityServer configuration store
- IdentityServerPersistedGrantDbContext: for IdentityServer operational store
Run entity framework migrations:

Visual Studio command line (Nuget package manager):

Migrations for Asp.Net Core Identity DbContext:

Add-Migration AspNetIdentityDbInit -context AdminIdentityDbContext -output Data/Migrations/Identity
Update-Database -context AdminIdentityDbContext

Migrations for Logging DbContext:

Add-Migration LoggingDbInit -context AdminLogDbContext -output Data/Migrations/Logging
Update-Database -context AdminLogDbContext

Migrations for IdentityServer configuration DbContext:

Add-Migration IdentityServerConfigurationDbInit -context IdentityServerConfigurationDbContext -output Data/Migrations/IdentityServerConfiguration
Update-Database -context IdentityServerConfigurationDbContext

Migrations for IdentityServer persisted grants DbContext:

Add-Migration IdentityServerPersistedGrantsDbInit -context IdentityServerPersistedGrantDbContext -output Data/Migrations/IdentityServerGrants
Update-Database -context IdentityServerPersistedGrantDbContext

Or via `dotnet CLI`:

Migrations for Asp.Net Core Identity DbContext:

dotnet ef migrations add AspNetIdentityDbInit -c AdminIdentityDbContext -o Data/Migrations/Identity
dotnet ef database update -c AdminIdentityDbContext

Migrations for Logging DbContext:

dotnet ef migrations add LoggingDbInit -c AdminLogDbContext -o Data/Migrations/Logging
dotnet ef database update -c AdminLogDbContext

Migrations for IdentityServer configuration DbContext:

dotnet ef migrations add IdentityServerConfigurationDbInit -c IdentityServerConfigurationDbContext -o Data/Migrations/IdentityServerConfiguration
dotnet ef database update -c IdentityServerConfigurationDbContext

Migrations for IdentityServer persisted grants DbContext:

dotnet ef migrations add IdentityServerPersistedGrantsDbInit -c IdentityServerPersistedGrantDbContext -o Data/Migrations/IdentityServerGrants
dotnet ef database update -c IdentityServerPersistedGrantDbContext

Migrations are not a part of the repository - they are ignored in .gitignore.

We suggest to use seed data:

In Program.cs -> Main, uncomment DbMigrationHelpers.EnsureSeedData(host) or use dotnet CLI dotnet run /seed
The Clients and Resources files in Configuration/IdentityServer are the initial data, based on a sample from IdentityServer4
The Users file in Configuration/Identity contains the default admin username and password for the first login

Using other database engines - PostgreSQL, SQLite, MySQL etc.

Follow these steps for setup other database engines

Authentication and Authorization

Change the specific URLs and names for the IdentityServer and Authentication settings in Constants/AuthenticationConsts or appsettings.json
Constants/AuthorizationConsts.cs contains configuration of constants connected with authorization - definition of the default name of admin policy
In the controllers is used the policy which name is stored in - AuthorizationConsts.AdministrationPolicy. In the policy - AuthorizationConsts.AdministrationPolicy is defined required role stored in - AuthorizationConsts.AdministrationRole.
With the default configuration, it is necessary to configure and run instance of IdentityServer4. It is possible to use initial migration for creating the client as it mentioned above

Login Configuration

In Skoruba.IdentityServer4.STS.Identity - in appsettings.json is possible to specify which column will be used for login (Username or Email):

  "LoginConfiguration": {
    "ResolutionPolicy": "Username"
  }

or using Email:

  "LoginConfiguration": {
    "ResolutionPolicy": "Email"
  }

Register Configuration

In Skoruba.IdentityServer4.STS.Identity - in appsettings.json is possible to disable user registration (default: true):

 "RegisterConfiguration": {
    "Enabled": false
  }

Localizations - labels, messages

All labels and messages are stored in the resources .resx - locatated in /Resources
- Client label descriptions from - http://docs.identityserver.io/en/latest/reference/client.html
- Api Resource label descriptions from - http://docs.identityserver.io/en/latest/reference/api_resource.html
- Identity Resource label descriptions from - http://docs.identityserver.io/en/latest/reference/identity_resource.html

Tests

The solution contains unit and integration tests.
Stage environment is used for integration tests:
- DbContext contains setup for InMemory database
- Authentication is setup for CookieAuthentication - with fake login url only for testing purpose
- AuthenticatedTestRequestMiddleware - middleware for testing of authentication.
If you want to use Stage environment for deploying - it is necessary to change these settings in StartupHelpers.cs.

Overview

Solution structure:

STS:
- Skoruba.IdentityServer4.STS.Identity - project that contains the instance of IdentityServer4 and combine these samples - Quickstart UI for the IdentityServer4 with Asp.Net Core Identity and EF Core storage and damienbod - IdentityServer4 and Identity template
Admin UI:
- Skoruba.IdentityServer4.Admin - ASP.NET Core MVC application that contains Admin UI
- Skoruba.IdentityServer4.Admin.BusinessLogic - project that contains Dtos, Repositories, Services and Mappers for the IdentityServer4
- Skoruba.IdentityServer4.Admin.BusinessLogic.Identity - project that contains Dtos, Repositories, Services and Mappers for the Asp.Net Core Identity
- Skoruba.IdentityServer4.Admin.BusinessLogic.Shared - project that contains shared Dtos and ExceptionHandling for the Business Logic layer of the IdentityServer4 and Asp.Net Core Identity
- Skoruba.IdentityServer4.Admin.EntityFramework - EF Core data layer that contains Entities for the IdentityServer4
- Skoruba.IdentityServer4.Admin.EntityFramework.Identity - EF Core data layer that contains Entities for the Asp.Net Core Identity
- Skoruba.IdentityServer4.Admin.EntityFramework.DbContexts - project that contains DbContexts for the IdentityServer4, Logging and Asp.Net Core Identity
Tests:
- Skoruba.IdentityServer4.Admin.IntegrationTests - xUnit project that contains the integration tests for AdminUI
- Skoruba.IdentityServer4.Admin.UnitTests - xUnit project that contains the unit tests for AdminUI
- Skoruba.IdentityServer4.STS.IntegrationTests - xUnit project that contains the integration tests for STS

The admininistration contains the following sections:

IdentityServer4

Clients

It is possible to define the configuration according the client type - by default the client types are used:

Empty
Web Application - Server side - Hybrid flow
Single Page Application - Javascript - Authorization Code Flow with PKCE
Native Application - Mobile/Desktop - Hybrid flow
Machine/Robot - Resource Owner Password and Client Credentials flow
TV and Limited-Input Device Application - Device flow
Actions: Add, Update, Clone, Remove
Entities:
- Client Cors Origins
- Client Grant Types
- Client IdP Restrictions
- Client Post Logout Redirect Uris
- Client Properties
- Client Redirect Uris
- Client Scopes
- Client Secrets

API Resources

Actions: Add, Update, Remove
Entities:
- Api Claims
- Api Scopes
- Api Scope Claims
- Api Secrets
- Api Properties

Identity Resources

Actions: Add, Update, Remove
Entities:
- Identity Claims
- Identity Properties

Asp.Net Core Identity

Users

Actions: Add, Update, Delete
Entities:
- User Roles
- User Logins
- User Claims

Roles

Actions: Add, Update, Delete
Entities:
- Role Claims

Application Diagram

Plan & Vision

1.0.0:

1.1.0:

Docker support (#121)
Add audit logs to track changes (#61)
Create a project template using dotnet CLI - dotnet new template
- Second template: The administration of the IdentityServer4 (without Asp.Net Core Identity) (#79)