Skip to main content

A Demo On Azure AD B2C Authentication In MVC Application[.NET 6]

In this article, we are going to do a demo on Azure AD B2C authentication in the MVC application[.NET 6].

Azure AD B2C Configuration Steps:

Step1:
Login into Azure Portal(https://portal.azure.com/)

Step2:
Chose the directory that has the subscription(eg: free, student, pay-as-you-go, etc).

(1) Select the 'Directories + Subscriptions' on the azure portal menu.
(2) Left side menu select 'Directories + Subscriptions'. Bottom select 'All Directories' tab where we can select all directories we have the option to 'switch'.
Here I have only one directory that has my subscription. So if we have multiple directories then we can see a 'switch' option.
Step 3:
The 'Microsoft.AzureActiveDirectory' resource provider needs to register with our 'subscription'.

(1) On the Azure portal home page select 'Subscriptions'.

(2) Now select your appropriate subscription.
(3) Search 'Resource Provider' and then 'Microsoft.AzureActiveDirectory' should be registered.
Step 4:
Create Azure AD B2C tenant.

(1)Click on 'Create a resource' on the azure home page.
(2)Search and select 'Azure Active Directory B2C'.

(3) Click on the 'Create' button.

(4) Chose any one option from 'Create New Azure Active Directory B2C' or 'Link an existing  Azure Active Directory B2C into your subscription'.
(5)Create a tenant.
  • Organization Name - Enter the name of your organization.
  • Initial Domain Name - By default, the basic domain name at 'onmicrosoft.com' is included with your directory. Later, you can add a domain name that your organization.
  • Country/Region -  Select the nearest server location to you.
  • Subscription - select your subscription.
  • Resource Group - Create a new group if you don't have any existing Resource Group.
  • Resource Grop Location.
Step 5:
So click on the 'Directories + Subscriptions' menu and then 'switch' to our newly-created directory.
Step 6:
After switching to the directory, on the azure landing portal, search and select 'Azure AD B2C'.
Step 7:
Register a web application.

(1) Left menu under 'Manage' select the 'App Registrations' and then click on 'New Registration'.

(2)Fill up the App registration form
  • Name - A display name for the application.
  • Support account types - use the default selection(last radio button option).
  • In the 'Redirect URL' section, select the dropdown value as 'Web', and in the text box enter our MVC(or any web application) URL.(Local development we can register 'localhost' so this URL can be updated any time later also)
  • Check the 'Permission' check box.
(3) After successful Application registration we can observe a generated 'Application Id' which we have to use in our MVC application in later steps.
Step 8:
Create a Client Secret.

(1) Left side menu under 'Manage' select 'Certificates & Secrets'. Next click on 'New Client Secret'. Next on popover enter the description for the secret and click on 'Create'.
(2) On successful creation secrets can be viewed like below.
Step 9:
Enable Tokens

(1) Under 'Manage', select 'Authentication' tab, then enable the 'Access Token' & 'ID Token'.
Step 10:
Create User flow for Sign-in &Sign-up.

(1) In 'Azure AD B2C', under the 'Policies' select 'User Flows'. Next click on the 'New User Flow'.

(2) Now let's create a user profile for Sign-in&Sing-up.
(3) Complete the user flow form.
  • Name - Register a name for our flow
  • Identity Providers - Select 'Email Signup' means option for email & password login.
  • Multifactor authentication & Conditional Access options can be left default.
  • User attributes are values collected on sign-up. Claims are values about the user returned to the application in the token. You can create custom attributes as well.

Create A .NET6 MVC App With Azure AD B2C Authentication:

Let's create a .Net6 MVC sample application with individual Azure AD B2C authentication to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor.
CLI command
dotnet new mvc -o Your_Project_Name -au IndividualB2C

Configure Azure AD B2C Settings In appSettings.json:

let's configure the Azure AD B2C Settings in appSettings.json.
"AzureAdB2C": {
    "Instance": "",
    "ClientId": "",
    "Domain": "",
    "SignedOutCallbackPath": "",
    "SignUpSignInPolicyId": "",
    "ResetPasswordPolicyId": "",
    "EditProfilePolicyId": "",
    "CallbackPath": ""
},
Instance:
In 'Azure AD B2C', select 'App registration' next select 'Endpoints'. Copy the domain name from the urls on the popover.
eg: Instance: "https://naveenbommiditechseeker.b2clogin.com"

ClientId:
Registered Application Id
Domain:
In 'Azure AD B2C', Domain name value.
SignedOutCallbackPath:
The 'SignedOutCallbackPath' value must be '/signout/{your_signout_flow_name}'. Here in the path 'signout' keyword is fixed string.
eg: SignedOutCallbackPath: "/signout/B2C_1_Sign_SignUp_1"

So in 'Azure AD B2C' under 'Policies' select 'Users Flows' and copy the name of the signout flow.
SignUpSignInPolicyId:
Directly assign the name of 'SignIn&SingOut' policy.
eg: SignUpSignInPolicyId : "B2C_1_Sign_Signup_1"

ResetPasswordPolicyId & EditProfilePolicyId:
Similarly like 'SignIn&SingOut' policy we can create for 'ResetPasswor' and 'EditProfile' then asing those policy names

CallbackPath:
A fixed string that is '/signin-oidc'. This path should be in redirect URLs registered in the 'App Registration' of the 'Azure AD B2C'

Test Authentication Flow:

(1) Run the application and click on 'Login'

(2) Now it redirects us to our Azure AD B2C authentication domain that loads the login page.
and then click on 'Sign-Up'
(3) Register our user into the 'Azure AD B2C'.
(4) Now after registration we successfully logged into the application.

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information on Azure Active Directory B2C Authentication in .NET6 MVC application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

  1. my signout button is not coming why ??

    ReplyDelete
  2. Thanks! Can you tell me how we can redirect to another URL after successfully signing in ?

    ReplyDelete

Post a Comment

Popular posts from this blog

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update data for their respective clients. Some of the Key Characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-ONly cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use the authentication with HTTP-only JWT cookie then we no need to implement the custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually