Each API has a separate scope from the associating Azure App registration. The application accepts two different access tokens from the same Azure B2C identity provider.
The APIs are implemented using ASP.NET Core and this uses Azure B2C to validate and authorize the access tokens. An ASP.NET Core Razor page application is used for the UI, but this can be any SPA, Blazor app or whatever the preferred tech stack is. The ASP.NET Core applications only use Azure B2C to authenticate and authorize. Implement certificate authentication in ASP.NET Core for an Azure B2C API connector.Add extra claims to an Azure B2C user flow using API connectors and ASP.NET Core.Using Azure security groups in ASP.NET Core with an Azure B2C Identity Provider.Securing ASP.NET Core Razor Pages, Web APIs with Azure B2C external and Azure AD internal identities.The authorization implementation which forces this, is supported using an ASP.NET Core policy with a handler. Only identities from the Azure AD tenant can use the administrator API. Two APIs are implemented, one for users and one for administrators. Azure B2C uses the signin, signup user flow and allows identities to authenticate using an Azure AD single tenant.
This article shows how to implement an ASP.NET Core Razor page to authenticate against Azure B2C and use Web APIs from a second ASP.NET Core application which are also protected using Azure B2C App registrations.
0 kommentar(er)
