openiddict-core VS Avalonia.FuncUI

Openiddict is also an option. Check it out.https://github.com/openiddict/openiddict-core

To implement an OAuth server together with OpenID connect specification, I used a free and open source framework called Openiddict. You should checkout their GitHub repository at github.com/openiddict/openiddict-core. It is a nice and feature rich tool which help you get started very fast. However, comparing to alternatives like identity server, it needs more implementation rather functionalities coming out of the box.

You can use Openidict https://documentation.openiddict.com/, give it a try

Openiddict to create your own OpenID Connect server if you want to deep dive into auth https://github.com/openiddict/openiddict-core

If you do want a .NET IdP then you could look into OpenIddict but will require some hands on work, at a minimum authorisation controllers. If you're looking for something more out of the box OrchardCore's OpenId module might be better for you.

I personally prefer using Cookies with openiddict.

Also, the OAuth bit is very cool!! Do you plan to support OpenIddict it’s a free federated identity server.

Okta is a great example of an IdP, although there are many others. Auth0, Ping Federate, Amazon cognito, etc. OP also mentioned Identity Server, which is a framework for implementing your own IdP. I've also personally used an open-source library called [OpenIDDict[(https://documentation.openiddict.com/) to great success. I would highly recommend attempting to implement one of these providers as a learning exercise.

For those interested in .NET languages with alternative compilation targets, Elmish (https://elmish.github.io/elmish/) is pretty unique.

We use F# on the front end (instead of TS), and thanks to the Fable compiler (which transpiles F# to JS, Python, Dart, PHP and Rust), most of the benefits of an Elm-style model in the UI can be ported to all sorts of different outputs languages. The rust target is in beta, but its promising because the WASM bundle size stands to be dramatically lower.

While the default is reactivity library for Elmish is React, you can swap in Avalonia/FuncUI (https://github.com/fsprojects/Avalonia.FuncUI) pretty easily as well.

The code to declare/build the widgets is quite nice. Modifying widgets by hand on certain signals or manually re-wiring all the signals seems a bit outdated to me.

Wonder if something like FuncUI [1] could be built on top of it.

[1] https://github.com/fsprojects/Avalonia.FuncUI

OTOH, if desktop really is the primary focus, and if you can drop the idea of reusable UI code, then Avalonia is a great choice for F# as you can use a Avalonia.FuncUI and/or Elmish.Avalonia.

And one more MVU for you https://github.com/fsprojects/Avalonia.FuncUI

You might want to check out Avalonia.FuncUI, which lets you use F# and the cross-platform Avalonia framework to build desktop applications with an Elm-like architecture: https://github.com/fsprojects/Avalonia.FuncUI#example-using-...