Understanding the Auth0 Application Limit

Rhythm’s hosted Auth0 configuration supports up to 10 Auth0 Applications per customer tenant. The Rhythm Console and Rhythm Portal each consume 1 application, leaving 8 available for customer use. 

What Counts as an “Application” in Auth0?

In Auth0, an Application typically includes:

• Single Sign-On (SSO) integrations

• Single Page Applications (SPA)

• Regular Web Applications

• Machine-to-Machine (M2M) integrations

• Any integration that requires its own Auth0 client credentials (client ID and client secret)

Some vendor integrations may require two applications — for example, one for SSO and another for API access.

Can the Limit Be Increased?

The 10-application limit is defined by the Auth0 plan used for Rhythm-hosted tenants. It cannot be increased within the hosted configuration.

If additional applications are required, there are two available options.

Option 1: Reuse an Existing Application

In some cases, multiple integrations can share a single Auth0 application. This can reduce the total number of applications used when the integrations’ credential and security requirements allow sharing.

Important considerations:

• Rotating or disabling credentials will affect all integrations using that application

• Not all integrations are appropriate for shared credentials

• Integrations that require strict separation may need their own application

Rhythm can help determine whether reuse is appropriate for a specific integration.

Option 2: Use a Dedicated Auth0 Tenant

If you require:

• More than 8 applications, or

• Strict separation between integrations and credentials

You may choose to use your own Auth0 tenant and Auth0 agreement. This provides greater flexibility and independent scaling.

Rhythm can advise on the approach and required steps.

Planning Ahead

When evaluating new integrations, consider:

• Whether the integration requires unique client credentials

• Whether it involves API access that sends data back to Rhythm

• Whether separate credential rotation or isolation is required

• Whether additional integrations are expected in the future

Early planning can help prevent reaching the application limit unexpectedly.

Questions?

If you are unsure whether a new integration will require an additional Auth0 application, contact Rhythm Support and include:

• The vendor name

• Whether SSO is required

• Whether API access is required

We can review the integration requirements and recommend the appropriate approach.