[Feature] Configure through the web UI

[jthomperoo]

Feature description

It would be nice to be able to configure things through the web UI.

• View/Add/Remove clients
• View/Add/Remove users

Motivation

From: #13 (comment)

Alternatives considered

Environment only config exists, but this would allow things to be used in a more dynamic way at runtime.

[JWMB]

I started looking at this, but not sure I'm the right person to implement it... Either Razor syntax and editor support is still lousy in VS2026 or I'm doing it wrong :)

[JWMB]

It's official, I shall never learn to love Razor! An angry first (draft) attempt at Create/Update users (no backing store) here:
https://github.com/JWMB/dev-oidc-toolkit/pull/1/changes

[JWMB]

Tried to move the editor code into a generic component, but documentation is too poor and Intellisense has just given up so it's like flying without wings (i.e. crashing). (Is natural unsigned int, nuint, super popular in Razor pages?)

[JWMB]

I think I now have enough of a prototype to keep me going for a bit, but it's definitely low-quality and non-idiomatic code (still feel I know nothing about Razor).
/Users and /Clients now have auto-generated forms, and most importantly, JSON input fields. This way I can keep definitions handy and register them quickly even though there's no persistance.

[jthomperoo]

I've added a really barebones implementation for adding users and clients at runtime, it's pretty limited, but I think we can take it as a base and expand it with more fields as we need, it looks similar to your implementation. You can see it in #18

[jthomperoo]

Thanks for the feature request! This is now available in 0.5.0.

Let me know if this works for you, and if there's other fields you would like to see added in.

[JWMB]

Let me know if this works for you, and if there's other fields you would like to see added in.

Thanks - works, but I must say I generally prefer auto-generated forms (from dotnet types or OpenAPI descriptions) to hand-rolled ones. My implementation above is a quick hack (and has no rendering of validation attributes yet), but I think it's the correct path unless there are very specific requirements on the form.
I also like having JSON inputs. Sure, one can edit HTTP requests, but a GUI for it is pretty handy.

[jthomperoo]

Ah, interesting, I didn't realise this auto-generated form approach; let me have a play around and see if we can switch to that.

[JWMB]

Improving a bit on the generator rn, with HTML validation (min/max/pattern etc) based on the property CustomAttributes (or overrides defined on call-site)

e.g.

new FormGenerator.RenderOverride { PropertyName = nameof(DevOidcToolkitUser.FirstName), ModifyInfo = pi => pi.MinLength = 1 }

renders