Skip to main content

Setup Azure AD B2C

Azure Active Directory B2C

Briefly, Azure Active Directory (Azure AD) B2C is a business-to-consumer identity management service. This service enables you to customize and control how users securely interact with your web, desktop, mobile, or single-page applications. Using Azure AD B2C, users can sign up, sign in, reset passwords, and edit profiles. Azure AD B2C implements a form of the OpenID Connect and OAuth 2.0 protocols. The important key in the implementation of these protocols is the security tokens and their claims that enable you to provide secure access to resources.

Ingredients for set up an Azure AD B2C resource

Ingredients that you need to have in-order to set up an Azure AD B2C
  • Microsoft Azure account with a valid subscription associated.
  • Azure AD B2C tenant resource with necessary policies

Directions

I hope that you have a Microsoft Azure account with a valid subscription associated. If you don't have an account, create an account with the support of the link provided here. 

If you don't have an Azure AD B2C tenant resource already that would be the next step. Follow the steps given here.

I hope you have linked your Azure AD B2C tenant resource to your Azure subscription. If you read the link given in the above paragraph, you should have already linked it.

You will be able to see your Azure AD B2C tenant resource in your "All resources" page. If it is visible, you can switch to the newly created directory, else, refresh your browser window, then check the "All resources" page again.

Go to the All resources page to find new Azure AD B2C resources.

Switch to newly created Azure AD B2C directory.
In your new directory click on the "All services" page

All Services will list down available services in the directory.
and then type "b2c" on the search area and you will see a service called "Azure AD B2C" on the result list. Click on that and it will redirect to the overview page of the Azure AD B2C service.

Overview page of Azure AD B2C service

Make sure your Domain name, Subscription ID and the Resource name are correct.

You are now qualified to authenticate your app with Azure AD B2C resource.

May the force be with you! 
Labels:

Comments

Post a Comment

Popular Posts

SSAS: The Sort Order Specified For Distinct Count Records Is Incorrect.

Symptoms During a processing time of a cube that contains a distinct count measure, the process fails with the following error message: The sort order specified for distinct count records is incorrect Cause This is most likely caused by different sort order used on the data warehouse data set and the analysis service database data set. Resolution Modify the sort order of the data warehouse data set so that it will match with the analysis service database data set. Into the Depth  Navigate to the analysis database and start to process the desired database. When the processing begins, the Process progress window will pop up. Wait till the process gets failed. After the process failed, find the failing measure group and expand to the last node where you can see an SQL query. Double click on the query and view the details. This query gives you the exact order by the column which caused you this trouble.  Execute the query using the data warehouse datab...
Post a Comment
Read more

global.json file

  Symptoms Suddenly you get build errors in your build pipeline which perfectly builds in your local machine 🤔🤔🤔 Cause Most likely the root cause is .NET SDK versions. Your local machine builds on a different SDK and the pipeline builds on a different SDK. Resolution The ideal way of solving this is to force everyone to use one define .Net SDK. Regardless of whether it is a developer or CI pipeline. Simply to make this happen .NET  provides you a file called "global.json". The global.json file allows you to define which .NET SDK version is used when you run .NET CLI commands. Selecting the .NET SDK version is independent from specifying the runtime version a project targets. For information about specifying the runtime version instead of the SDK version, see Target frameworks . If you always want to use the latest SDK version that is installed on your machine, no global.json file is needed. Into the Depth The sample global.json file looks like the below, {    ...
Post a Comment
Read more

React: åäö swedish characters shown as �

Last few months, I have started working on a web application that belongs to a Swedish client. Since this application's target audience is Swedish people, we were only focused on the Swedish language as the application language. We have hardcoded all the labels (I know it is not a good practice but for this case that was fine 😉). Then we figured out something is wrong when it rendered in the HTML. Symptoms All the special Swedish characters were rendered as � åäö Swedish characters shown as � Cause This is most likely caused by the encoding.  Resolution Ideally, you can overcome this issue by providing a metadata tag for  "charset".   In your   index.html   file, add the following meta tag to the header section. < meta charset = "UTF-8" > Simply, when you declare the "charset" as "UTF-8", you are telling your browser to use the UTF-8 character encoding, which is a method of converting your typed characters into ma...
Post a Comment
Read more