Use Stack Overflow to get support from the community. Ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before. Make sure that your questions or comments are tagged with [azure-ad-b2c]. If you find a bug in the sample, please raise the issue on GitHub Issues. To provide product feedback, visit the Azure Active Directory B2C Feedback page.
User will not be prompted for 'Loyalty number' during registration. But will be progressively prompted for it during sign-in.
-
You can automate the pre requisites by visiting the setup tool if you already have an Azure AD B2C tenant. Some policies can be deployed directly through this app via the Experimental menu.
-
You will require to create an Azure AD B2C directory.
-
To use the sample policies in this repo, follow the instructions here to setup your AAD B2C environment for Custom Policies.
-
For any custom policy sample which makes use of Extension attributes, follow the guidance on storing the extension properties and adding the application objectID. The
AAD-CommonTechnical profile will always need to be modified to use yourApplicationIdandObjectId.
When the user signs in if 'extension_LoyaltyNumber' doesn't exist and if its not a 'newUser' they will be directed to 'SelfAsserted-ProfileUpdate' to update the Loyalty number.
- During registration - Loyalty number will not be prompted.
- During sign-in - you will be forced to enter a loyalty number.
This sample policy is based on LocalAccounts starter pack. All changes are marked with Sample: comment inside the policy XML files. Make the necessary changes in the Sample action required sections.