Integrating with OpenIddict

Identity schema

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: You should back up your users before proceeding as there is no rollback script

We have provided a SQL script for migrating a ASP .Net Identity schema to our extended one. This will need to be done for AdminUI to run against you OpenIddict database.

This schema is available on nuget using the IdentityExpress.Identity package. An AdminUI OpenIddict integration example is also available to demonstrate a working OpenIddict 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>();

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

Scopes and Applications claims

You need be able to use the claims binded to Scopes and Applications in AdminUI from your OpenIddict server. You can find the complete documentation here.