Azure AD B2C Unboxing

 It’s relatively easy to get started with integrating B2C authentication into your own applications.

First get a B2C tenant

For this you will need an Azure user and an Azure subscription - if you don't have a user account or you want to keep it separate from your existing accounts, you can create one at outlook.com.  Then you will need to head over to portal.azure.com and sign up with Azure.

Once that's done, click "create a resource" in Azure and search for B2C in the search bar.  Click on "Azure Active Directory B2C".  You will be taken to a page with a create button - hit that!


Integrate your application

B2C will integrate with existing SAML or OpenID Connect applications.  But if you’re starting from scratch or porting an in-house application, it is useful to get sample code from the Microsoft documentation site (available in multiple flavours). 

The latest samples (as of August 2022) target 18 different platforms (admittedly some of them are different flavours of .Net – but that’s a useful advantage as it covers traditional .Net and .Net Core):

https://docs.microsoft.com/en-us/azure/active-directory-b2c/integrate-with-app-code-samples

Once you have the sample loaded into Visual Studio there are relatively few changes you need to make in order integrate with your B2C tenant.

 

Comments

Post a Comment

Popular posts from this blog

Microsoft CIAM debuts at Build 2023

Image
For a long time we've been aware of Microsoft's efforts towards converging Azure Active Directory B2C and Azure Active Directory. They are making this change in order to provide a single stable product for the back end portal and other aspects of these identity services.  New developments will see a 'CIAM' product sitting on top of AAD - this replaces (or will eventually replace) B2C.   CIAM will also provide better experiences for developers hoping to build user journeys (sign in, sign up, etc.). Microsoft continues to support AAD B2C.  At time of writing it provides a fuller feature set.  However, B2C as-is will eventually retire, and migration paths will be important. The CIAM solution will offer more back-end management features, and an event-driven programming paradigm for user journeys. I will make more information available as and when!
Read more

LinkedIn now uses Verified ID for Employee verification

Image
  Microsoft Verified ID is a digital identity verification solution that enables individuals to obtain digital "credentials" from organisations that know them, or more accurately, that know some aspect of their identity.  For example, their name, their educational qualifications, or in this case, their employment status.  These credentials can then be shared with third-party organizations, such as employers or educational institutions, in a secure and trusted manner.  LinkedIn, which is owned by Microsoft, has integrated with Microsoft Verified ID to allow LinkedIn members to verify their employment status. Using this new integration, employers can create a custom process for verifying employees, and employees, once they have done this, can present the credential to LinkedIn in order to obtain the new green "check mark" on their LinkedIn profile. Currently this requires the LinkedIn app - at time of writing there is no announcement yet about migrating this feature t
Read more

Keeping safe beyond sign-in

Image
As The Register reports today , Microsoft briefly exposed a plethora of passwords and other secrets due to a bulk upload of data to GitHub recently. The data was a set of AI training data - data used to teach AI models how to understand the world around them. It makes no sense having the best locks on your front door if you leave the back door open... so what can we learn from this episode? Protecting passwords and other sensitive information from exposure to the wider world is essential for maintaining your online security. Here are some measures you can take: Use Strong, Unique Passwords: Create strong, complex passwords that are difficult to guess. Use a combination of uppercase and lowercase letters, numbers, and special characters. Avoid common dictionary words or phrases. Ensure your passwords are at least 12-16 characters long. Use a passphrase, which is a sequence of random words or a sentence that's easy to remember but hard to crack. Use a Password Manager: A password man
Read more