This page describes the typical architecture scenarios we have identified when working with customers on implementing Auth0.
The first set, called Application Configurations, describes the typical application implementation patterns.
The second set, called Business Scenarios, describes the architecture depending on the type of businesses, whether that be B2C (Business to Consumer applications), B2B (Business to Business applications), B2E (Enterprise applications), or a combination of B2B and B2E. Click on any scenario to get more information.
These scenarios describe the different type of technology architectures you application may use, and how Auth0 can help for each of those
Mobile + API
Mobile Application ("Client") which talks to an API ("Resource Server"). The application will use OpenID Connect with the Authorization Code Grant using Proof Key for Code Exchange (PKCE) to authenticate users.
Server Client + API
Server to server communication where a server “Client” needs to make secure calls to an API (“Resource Server”), but on behalf of the client vs. a user.
SPA + API
Single Page Web Application "Client" which talks to an API ("Resource Server"). The application will use OpenID Connect with the Implicit Grant Flow to authenticate users with Auth0.
Single Sign-On for Regular Web Apps
Traditional web application which needs to authenticate users using OpenID Connect.
Regular Web App (using SAML)
Traditional web application which needs to authenticate users using SAML2
These scenarios describe the type of businesses which implement Auth0, and how Auth0 can help in each of those business scenarios
Business to Business + Enterprise Identity Scenarios
This is essentially a hybrid between B2B and B2E where you have a larger SAAS application, like Zendesk for example, where users are grouped into companies.
Business to Business Identity Scenarios
In this scenario you usually have a larger SAAS application, like Zendesk for example, where their customers are typically other companies which are registered as tenants.
Business to Consumer Idenity Scenarios
Usually eCommerce or SAAS applications which have end users (consumers) as customers and the application typically used OpenID Connect as a protocol to communicate with Auth0.
Business to Enterprise Identity Scenarios
Large organization who wants to federate their existing enterprise directory service to allow employees to log in to applications using their existing enterprise credentials.