What are the choices for the administration of the Duende IdentityServer

[FrqSalah]

Hello,

My company was using IdentityServer4 with Skoruba for administration. We have recently started migrating to Duende IdentityServer 7.1, and I have some questions regarding the administration solution.

Migrating our current application has proven to be quite complicated because the existing database has been modified and does not conform to the expected format. Therefore, I am wondering if there are any effective solutions for managing administration, as we are currently stuck with the older version of Skoruba Identity Administration.

How have you managed similar migrations? What administration solutions have you found effective with Duende IdentityServer 7.1? Any tips or best practices you can share would be greatly appreciated.

[maartenba]

In terms of admin UIs, there's the commercial https://www.identityserver.com/products/adminui from Rock Solid Knowledge, and the OSS admin UI from Jan Škoruba and friends https://github.com/skoruba/Duende.IdentityServer.Admin - both compatible with Duende IdentityServer.

You could also choose to configure your IdentityServer in code (defining clients, APIs, resources, ...) so the configuration becomes versioned with your code, or consider a tailored UI that targets just the properties you want to expose instead of all of the options available.

[devployment]

Are there any plans to provide either a built in admin ui or provide a complete management API?

Duende.IdentityServer.Configuration is a poc at best I'd say.

The existing solutions are a pita at best. I guess Duende puts it best on their own here

All above approaches have the issue that IdentityServer itself does not have a full read/write configuration store abstraction, which means they need to work against EF directly.

But especially the following would be much appreciated

This is something we want to fix. We are planning to add both configuration abstractions as well as APIs. This will make it very easy to create any kind of admin/config functionality like UIs, CLIs, automated setups via CI pipelines, dynamic client registration etc.

Especially after the "recent" (fierce) price increase something "announced" for years like a proper config API would be greatly appreciated.

[maartenba]

We're looking at a basic UI in the quickstart templates (being iterated on, not yet at the point where we can share).

[damianh]

years like a proper config API would be greatly appreciated.

We hear you loud and clear! While we can't commit to a timeline, this topic is active (as is much more).