B2B Connect - Enterprise - Auth0 Docs

The B2B Connect - Enterprise

Auth0 B2B Connect - Enterprise is an enterprise-ready, modular integration layer that adds Auth0’s B2B enterprise features (such as Single Sign-On (SSO), user provisioning using System for Cross-domain Identity Management (SCIM), and Universal Logout) to your existing authentication stack. With B2B Connect - Enterprise, you can add Auth0 B2B services on your existing authorization server and maintain control of token issuance, session management, and login while offering your B2B customers the option of using their enterprise identity provider (IdP) for user authentication.

Benefits

Why use B2B Connect - Enterprise? Whenever you set out to build products for B2B customers, you could build complex B2B identity tooling just to handle the foundational elements of onboarding and customer management. This work typically falls to a platform identity team that balances competing priorities. The result is constant pressure to make trade-offs across three structurally critical pillars:

  1. Maintain rigorous security and interoperability.
  2. Deliver a flawless customer onboarding and lifecycle experience.
  3. Unlock and enable innovation for your core product.

When you address these pillars, you typically have the option of two paths: migrate to a modern identity platform, or layer enterprise capabilities onto your existing stack. Migration is a proven path, but it carries significant lead time. For teams in need of enterprise features on a faster timeline, or for platforms in which full migration introduces unnecessary risk, B2B Connect - Enterprise offers a third way: Add enterprise-grade B2B capabilities without replacing your existing stack.

Use cases

B2B Connect - Enterprise supports advanced B2B identity scenarios without the need for re-platforming, including the following use cases to:

How it works

Auth0 B2B Connect - Enterprise sits between your application’s authorization server and your customers’ enterprise identity providers:

  1. The user initiates login in your application.
  2. Your application sends an authentication request to your authorization server using its existing flow.
  3. Your authorization server identifies the user as a B2B Connect - Enterprise user and routes the request to Auth0.
  4. Auth0 B2B Connect - Enterprise sends an authentication request to the user’s enterprise IdP (such as Okta, Microsoft Entra ID, Google Workspace, or PingFederate) using SAML or OpenID Connect (OIDC).
  5. The user authenticates with their corporate credentials at the enterprise IdP.
  6. The enterprise IdP returns a SAML assertion or OIDC token to Auth0 B2B Connect - Enterprise.
  7. Your authorization server returns its own token to your application.
  8. Your application validates the token and bootstraps its own session.
  9. The user is granted access to your application.

For the Application integration type, the app redirects directly to Auth0, removing the intermediate authorization server from the federation flow.

Supported enterprise connections

B2B Connect - Enterprise supports the following enterprise connections:

Integrate B2B Connect - Enterprise

You can integrate B2B Connect - Enterprise with the Create B2B Connect Integration wizard in Auth0 Dashboard, which establishes the topology. Your choice at Step 1 (Name and Type) in the wizard determines your entire integration path.

Type Integration Redirect to Auth0 from Auth0 SDK required Protocol
1 Custom authorization server Auth server Not required OIDC or SAML
2 Third-party managed authorization server Auth server Not required OIDC or SAML
3 Application (direct) Application Recommended OIDC

Configure customer onboarding

Self-Service Enterprise Configuration (SSEC) gives your B2B customers a guided flow to configure their enterprise IdP and claims mappings without requiring direct support from your team. To configure customer onboarding:

  1. In Auth0 Dashboard, navigate to B2B Connect. Under the Organizations tab, select Set up.
  2. Enter a name for your Self-Service Enterprise Configuration Profile.
  3. Optional. Add a description.
  4. Auth0 creates a User Attribute Profile (UAP) named after your SSEC Profile. Select Continue.
  5. Choose how you want to generate SSEC tickets:
    • API Integration
    • Auth0 Dashboard
  6. Select Done.

For information on the maximum number of SSEC profiles you can create per tenant, read Self-Service Enterprise Configuration.

Session management

IPSIE session expiry (OIDC)

Auth0 B2B Connect - Enterprise supports the IPSIE session_expiry claim for enterprise OIDC identity providers. When Auth0 receives a session expiry signal from an enterprise OIDC IdP, it includes the session_expiry claim in the token that returns to your authorization server. Use this claim to terminate downstream sessions in alignment with the enterprise IdP’s session policy.

Universal Logout

B2B Connect - Enterprise supports Universal Logout with Okta Workforce Identity, OIDC, and SAML connections you can enable in Auth0 Dashboard. Universal Logout cannot be configured by your B2B customers, but it must be enabled for them.

Delegated administration

B2B Connect - Enterprise also supports delegated administration through the My Organization API and UI components. With My Organization, you can build a self-service administration experience that lets your B2B customers manage their own Organization settings without contacting your team. B2B customers using the My Organization interface can:

Troubleshoot

Connection list is empty

If an Organization has enterprise connections enabled but has not been granted access to your B2B integration application, then your tenant administrators see no connections when viewing the Enterprise Connections tab in the Auth0 Dashboard. To resolve this issue: navigate to Auth0 Dashboard > Organizations and select your application and navigate to the Applications tab. Verify the relevant B2B Integration is listed. If it is missing, you may need to + Add Application. To use Local Resource Discovery via Webfinger, Per-Application Access must currently be disabled for the Organization.

B2B customer did not receive self-service ticket

If a B2B customer does not receive their onboarding ticket, create a new ticket. In B2B Connect - Enterprise, navigate to the Organizations tab, select the relevant Organization, and generate a new onboarding ticket.