Hi folks,
I'm looking into removing Azure B2C from a project of mine, for reasons relating to automation and such (which B2C is not yet very compatible with), but want to keep my auth work flows the same. So, I'm looking at ASP.NET Core Identity. Currently, we use B2C to secure our REST API server. We have a React SPA that redirects to B2C for tokens that we then use to access our REST API. I would be needing to implement a self-hosted replacement for B2C, basically. I see that my options appear to include ASP.NET Core Identity and IdentityServer4.
I'm a bit confused as to what each of these projects provide, though. It seems to me that they have a ton of overlap. For example, the official ASP.NET Core Identity documentation says to use IdentityServer4 if you're trying to secure a REST API. I even see that the official Visual Studio project templates use IdentityServer4 if you choose a Web Api project template and choose to enable single account authentication. But then on the IdentityServer4 documentation I see a section explaining how to then integrate IdentityServer4 back into ASP.NET Core Identity. This circular dependency / integration has me a bit confused.
So I come here for help with clarifying this ...
If I'm using IdentityServer4, why would I maybe want to use ASP.NET Core Identity? What does Identity provide on top of IdentityServer4?
As a beginner, the documentation has me very confused. Thanks!