Architecture Scenarios

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.

More Scenarios Coming Soon

These scenarios are under construction and will soon be updated. Some describe the different type of technology architectures your application may use, while others describe the type of businesses which implement Auth0, and how Auth0 can help in each of those scenarios.

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.

Read more

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.

Read more

Regular Web App (using SAML)

Traditional web application which needs to authenticate users using SAML2.

Read more

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.

Read more

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.

Read more

Business to Consumer Identity 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.

Read more

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.

Read more