SLASCONE uses Azure AD B2C as its internal identity provider (idP), which is a modern and secure identity management system for customer facing applications.
In the context of SLASCONE, access management and federation options need to be considered separately for its 3 different portals:
- Vendor Portal
- Customer Portal
- Reseller Portal
AZURE ACTIVE DIRECTORY vs AZURE ACTIVE DIRECTORY B2C
Azure AD B2C is a separate service from Azure Active Directory (Azure AD). It is built on the same technology as Azure AD, but for a different purpose. It allows businesses to build customer facing applications, and then allow anyone to sign up into those applications with no restrictions on user account.
The main reason SLASCONE uses Azure AD B2C is because of the Customer and Reseller portal. Your employees might exist in your Azure AD, but your customers and reseller do not.
Azure AD B2C offers a native login mode, which means that you can send an invitation to any of your employees, and request them to create a new account (signup).
However, if your organization is using Azure AD, it is more meaningful to enable a federation between your existing Azure AD and SLASCONE's Azure AD B2C in order to provide a single sign on.
CUSTOMER AND RESELLER PORTAL
When you invite your customers or resellers to SLASCONE, they can use either the native login mode (signup), or they can even sign in with their existing social or enterprise accounts, without having to create a new account just for accessing SLASCONE. It is up to you to decide which social or enterprise accounts are allowed.
BYPASSING AZURE ACTIVE DIRECTORY B2C
SLASCONE communicates only with AD B2C. All other identity providers are feasible through federation, but not directly. It is not possible to bypass AD B2C.