## Documentation

- About
- Read First
  - What is IdentityServer
  - Installation Scenarios
- Migrations
- Bootstrapping
- Configuration & Integration
  - AdminUI Settings
  - Configuring AdminUI
  - Configuring AdminUI (NuGet)
  - Integrating with Identity Server
  - Integrating with Identity Server Custom Schema
  - Integrating with Quickstarts
  - Enabling Logging
- Installation
  - Installer
  - IIS
  - Azure
    - Install in Azure
    - Create Azure Web App
  - Docker
  - NuGet
- Custom Database Connections
- Custom Identity Store
  - Overview
  - Partial Implementation
  - Full Implementation
  - Tenancy With Entity Framework
  - NoSql Implementation (MongoDB)
- Users
  - Searching for Users
  - Adding Users
  - Editing Users
  - Deleting Users
  - Merge Users
  - Set User Password
  - Session Management
  - User Reports
- Roles
  - Creating Roles
  - Managing Roles
  - Managing Users in a Role
- Claim Types
- Clients
  - Searching for Clients
  - Adding Clients
  - Adding a SAML Client
  - Adding a WS-Fed Client
  - Editing Clients
  - Deleting Clients
  - Clone Client
- Import and Export
  - Exporting Clients
  - Importing Clients
  - Importing Client Configuration with Secrets
  - Importing SAML Clients with Certificates
  - Import and Export Via the API
- Dynamic Authentication Providers
  - What is Dynamic Authentication
  - Enabling or disabling Dynamic Authentication
  - Add a Dynamic Provider
    - First Steps
    - Adding OIDC Provider
    - Adding SAML Provider
  - Edit a Dynamic Provider
    - Accessing edit view
    - Editing a OIDC Provider
    - Editing a SAML Provider
  - Deleting a Provider
  - Searching for Provider
- Resources
  - Searching for Resources
  - Creating Resources
  - Editing resources
- Webhooks
  - Webhooks
  - Endpoint Configuration
- User Settings Endpoints
- Access Policy
- Auditing
- FAQs
- Troubleshooting
  - Unable to load AdminUI web page
  - Unable to contact IdentityServer
  - Unable to contact API
  - Unable to log in

After using the IdentityServer Quickstarts to evaluate the framework, it is then possible to integrate AdminUI for production use.

Note: Quickstarts built using the ASP.NET Core Identity Visual Studio templates are not recommended for production, due to their fragility and abuse of anti-patterns.

AdminUI uses a custom ASP.NET Core Identity schema. This schema extends from the ASP.NET Core Identity Entity Framework defaults, which means any existing registration, password reset or login functionality will continue to work with the AdminUI user store.

Note: Existing users will need to be exported to use the AdminUI schema. For more details, see AdminUI Migrations.

This schema is available on nuget using the `IdentityExpress.Identity` package. An AdminUI IdentityServer integration example is also available to demonstrate a working IdentityServer installation using this nuget package and schema.

Use the following command to install using the nuget package manager console:

    install-package IdentityExpress.Identity

To use the AdminUI `IdentityExpress.Identity` schema, any existing ASP.NET Identity registrations need to be updated:

    // Register Identity using IdentityExpress entities and stores
    services.AddIdentity<IdentityExpressUser, IdentityExpressRole>()
      .AddUserStore<IdentityExpressUserStore>()
      .AddRoleStore<IdentityExpressRoleStore>()
      .AddIdentityExpressUserClaimsPrincipalFactory();

    // Register the DbContext for the IdentityExpress schema
    services.AddDbContext<IdentityExpressDbContext>();

Alternatively, there is a shortcut extension method:

    services.AddIdentityExpressAdminUiConfiguration()
      .AddIdentityExpressUserClaimsPrincipalFactory();

Any existing registrations for `SignInManager` or use of `IdentityUser` should also be updated.

Previous Next