Configures an existing B2C tenant for use with Identity Experience Framework custom policies. Performs all tasks defined in the get started document including creating a Facebook signing key required by some starter policies. The application creates a fake secret so that the starter pack policies referencing Facebook (those supporting social logins) can be loaded without errors. You will need to replace that key with your own if you plan on using Facebook for user accounts.
The application is deployed and ready to use:
- Enter the name of your B2C tenant
- Sign-in with an account with admin privileges in that tenant (account that was used to create the tenant has these by defualt)
- AzureAD will ask you to consent to the application having the ability to create objects in your tenant (applications, keys)
- Once you consent, the application will check whether your tenant has all the objects named in the Get started
- If these objects, do not exists, the application will create them (2 applications, 2 service principals and two keys)
- The final screen will display the relevant application ids needed in the IEF policies.
- If the application did not exist already, the final screen will provide a url link you should use to complete admin consent for the new applications to use each other item 9 in the Get started
- You can use the Enterprise Apps option of the Azure portal's AAD blade to remove the B2CIEFSetup service principal from your tenant (optional).
Once done, you can use some PowerShell tools to prepare your policies, edit them using VS Code with the B2C extension and upload them to the B2C tenant.