After a while I finally found a slot of time for writing this. Sorry for the long wait, and let’s get started!
This is the third part of my series of posts on how to use Azure B2C for authenticating a customer within Sitecore. You definitely want to have a look at part 1, in which I give the intro to the scenario we’re tackling here, and also part 2, in which we configure Azure B2C with the settings we will need here.
Today let’s go ahead and discuss the actual implementation of our way to validate Sitecore users as customers via Azure B2C. You may want to check part 1 to get a sense of what we will cover here.
Before you all hate me, as I was writing this post it became evident that we will need to cover the actual code in a third part of this series – setting up the B2C directory and explaining some things about how will our app work has taken more writing than I originally anticipated. So, bear with me, ok?
While AzureAD is not new, the new and exciting B2C brings new possibilities to the game. Centrally managing your customers and their profiles, abstracting away AzureAD stuff while still relying in its power and proven capabilities, gives you a flexibility that was not really there before.
With Sitecore being built to be easily extensible and extremely customizable, an integration between both systems was inevitable. Today, let’s talk about such integration by presenting a scenario, making a few assumptions, and finally deciding on an approach (Hint: it’s oAuth2 stuff).