Enabling Configuration Persistence

In the original Duende version of AdminUI Access Policies and Webhooks were stored in the DB to allow runtime modification in the AdminUI interface. This has become an optional feature of the OpenIddict version of AdminUI. As of version 3.3 you will be able to enable this. There are two steps to this process.

Step One: Create Database Table and Insert Empty Policy Record

The first step is to prepare your database to enable this, for this you will need to make changes to the Database that stores your OpenIddict tables (Application, Scope, etc) configuration. You can easily update the database with the AdminUI migrations tool. This is an example:

// Program.cs
var builder = WebApplication.CreateBuilder(args);

builder.Services
    .AddAdminUI(
        options =>
        {
            // override settings here
            options.MigrationOptions = OpenIddictMigrationOptions.AdminUI;
            ...
        }
    );

Alternatively, here is a set of scripts to provide and example. This is required as migrations and bootstrapping for the config store is not yet supported in the OpenIddict version of the product.

You can find a script for SQL Server, PostgrSQL, and MySQL here.

Step Two: Enable Persistence Using Feature Flag

The final step is to set FeatureFlags.EnableConfigurationPersistence to true and start AdminUI. You should now be able to modify the Access Policies and Webhooks in the AdminUI interface instead of providing them via the appsettings.