For the identity framework, we chose to use Azure AD B2C as our default identity provider. If you’d like to use another identity provider such as Azure AD or a different 3rd party tool, you can swap it out.
What does Azure AD B2C give us?
Azure AD B2C provides business-to-customer identity as a service. It enables you to easily authenticate users to your application using their preferred identity provider and is configurable to support a wide array of scenarios.
Azure AD B2C has two methods of configuring the business logic that users follow to gain access to your application: User Flows and Custom Policies. User Flows are predefined and are configured directly through the Azure AD B2C Web Portal. Custom Policies are XML based configuration files that are uploaded to the Azure AD B2C tenant.
The ASDK project uses Custom Policies to configure the Azure AD B2C tenant. The XML configuration that gets deployed can be found under the Saas.IdentityProvider folder within the repo, and you can read more about how to configure custom policies here.
When deploying the Azure AD B2C Identity Provider via the instructions found in the Quick Start guide, Azure AD B2C is configured to do the following:
- Provide a hosted SignIn and SignUp page that users can be directed to
- Reach out to the SaaS.Permissions.Service upon a user signing in to fetch their application permissions and roles
You can change or extend the behavior of the Azure AD B2C tenant that gets deployed with ASDK to do things like collect more information during signup, force users to enroll in Multi-Factor Authentication (MFA), and much more by modifying the custom policies.
App Roles and Global Admin
We are using App Roles to grant users “Global Admin” capabilities for the application. This App Role should only be granted to staff users that need it to administrate ALL the tenants across the entire SaaS solution. These roles are stored directly in Azure AD B2C and are returned in the JWT token claims when the user signs in.
How do I add a user to the default Global Admin role?
If you followed our steps in the Quick Start, the user that created the Azure AD B2C tenant will be automatically added to this global admin role. Follow these steps if you’d like to add additional users:
Switch to your Azure AD B2C Tenant in the Azure portal
Navigate to the Azure Active Directory menu
Click “Enterprise Applications”
Under the “Application Type” dropdown, select “All Applications” and click “Apply”
Select “Users and Groups” from the menu on the left
Click “Add user/group”
Select the users you’d like to add to the app role
Repeat steps 5-9, but on the
Design Considerations and FAQ
Q: Why did we choose Azure AD B2C?
- A: We chose Azure AD B2C because in additional to authenticating with “local” accounts, it can be easily extended to support a wide array of other identity providers such as Azure AD, GitHub, and many more. See the documentation for details.
Q: Why did we choose custom policies over user flows?
- A: User Flows are predefined and meant for more basic use cases. Custom Policies provide more support for automating the setup and deployment of the Azure AD B2C configuration, and generally provide greater extensibility in the long term for more complicated scenarios.
Q: Why are we only using Azure AD B2C App Roles for global administrator permissions? Why did we choose to put the tenant permissions in a special API?
- A: App roles in Azure AD B2C are nice, but too many of them get extremely complicated to manage. You can absolutely achieve application tenant permissions using just app roles, but we wouldn’t reccomend it if you are going to have more than just a handful of tenants. That’s why we chose to separate the application tenant permissions into a special API/data store that gets called during the user login flow.