AspNet.Security.OAuth.Providers VS ABP

This one here: https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers

Fortunately there is a good library that supports all kinds of oauth providers, so implementing Discord Oauth is now painless and follows the standard asp.net local authentication flow - link

There's even a community lib that gives you a ton of providers https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers to make things easier.

It's fairly simple to add an OAuth provider if you need to. Microsoft provides support out of the box for four (Microsoft, Google, Twitter, Facebook), and provide a nice guide. Aside from this, you can implement your own integration or use a prebuilt integration this repo has a really nice selection. The buttons to authenticate with the provider(s) will appear on the login page automatically.

In conclusion, ABP Suite is a game-changer in the realm of application development. Its modular design (comes from ABP Framework), powerful code generation, and support for modern frontend frameworks make it a go-to choice for developers looking to build scalable and feature-rich applications. Whether you are working on a small project or a large enterprise application, ABP Suite provides the tools you need to succeed in your development endeavors.

We use something like this at work: https://abp.io/

Take a look at abp.io. The framework is free and there is also a commercial version. It supports Blazor Server and WebAssembly UI layer.

Even better, try this version: https://github.com/abpframework/eShopOnAbp which is eShop on the ABP framework which I highly recommend.

We're using ABP and TinyMVVM along with the CommunityToolkit.Mvvm, working nicely.

Best i can think of is https://abp.io/

See the abp.io source code and document. Excellent documentation and well structured code.

I'd like to suggest ABP. Follow the getting started tutorial. They also blog about DDD things and offer some additional info and articles about it on the site and in the walkthrough.