Our great sponsors
-
active-directory-aspnetcore-webapp-openidconnect-v2
An ASP.NET Core Web App which lets sign-in users (including in your org, many orgs, orgs + personal accounts, sovereign clouds) and call Web APIs (including Microsoft Graph)
-
ASP.NET Core
ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I don't know what about that experience was bad. I'm sure you ran into issues, I'm sure it was a mix of asp.net core, AAD itself, and your own understanding (and maybe inconsistencies and bugs). Can you give a single example of something you found that was harder than it needed to be for the scenario you implemented? Bonus points if you can show what that would have looked like on a competing stack (but I don't really expect this...).
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.
That's true, I actually created a code generator for RepoDB with this in mind. It's still not stable and I haven't been able to work on it in a while, but at least it gets the job done similarly to the EF reverse engineering tool.
This is my project for my blog (still WIP, since I want to polish it properly) with the auth work I did for this application I spoke of without any of their business logic or styling. It uses RepoDB as an ORM, FluentMigrator for migrations and a user table that doesn't have all the fields that normally come in the default Identity db.