Our great sponsors
-
microsoft-identity-web
Helps creating protected web apps and web APIs with Microsoft identity platform and Azure AD B2C
-
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.
About 3 years ago, I wrote some code for a customer. It was as sample solution. The front end was as straight up ASP.NET Core MVC app. The backend API was a simple .NET Core API. Both made use ofOpen ID Connect (OIDC) and OAuth2 to authenticate users and acquire tokens in order to retrieve and update a ToDo list. The juice of the app is in the authentication. So in this blog post, we'll look how to take out the "old" authentication code and replace it with the latest and greatest in ASP.NET Core - Microsoft.Identity.Web. The blog will come in two parts:
After the migration
Related posts
- Implementing fine-grained access control with ASP.NET Core custom endpoint metadata
- Securing a .NET Azure Function with Azure AD
- Modernize your legacy API authentication with Microsoft.Identity.Web and Azure AD
- Another Authentication/Authorisation question
- Azure AD - How to have a Distributed Token Cache per tenant?