Auth0 tenant routing issue where a Single Page Application is being redirected to the wrong application during login despite correct client and connection settings.

Get Help
,
1

I have two applications in my Auth0 tenant:

  • one is a Single Page Application (SPA)

  • the other is a Regular Web Application

Even when I use the Auth0 Quickstart to set up the SPA with the correct Client ID, callback URLs, allowed origins, and enabled database connection, the login flow still redirects to the other application and shows a message like:

“Log in to [Other Application] to continue to [SPA].”

I have verified that:

  • The database connection is enabled for the SPA and disabled for the other application

  • No credentials, callback URLs, or origins overlap between the two applications

  • The SPA is correctly configured as a SPA in Auth0

  • The other application is correctly configured as a Regular Web App

  • Quickstart code uses the correct Client ID and domain

Despite this, Auth0 continues to route the SPA login flow through the other application.

This suggests there may be a tenant‑level default connection, default directory, rule/action, or legacy pipeline that is overriding the application‑level settings and forcing the SPA to authenticate through the other application.

Could someone from the community or Auth0 team help check whether there are any tenant‑level defaults, rules, actions, or legacy settings that could be causing this cross‑application routing?

3

Hi @mbin

Welcome to the Auth0 Community!

From what I understand, it appears that the message "Log in to [Other Application] to continue to [SPA]" is not an indicator of cross-application routing. This seems to be the default prompt generated by the New Universal Login template. It is dynamically constructed using your overarching Tenant Name (Friendly Name) . If you originally named your Auth0 Tenant after your first project (the Regular Web App), Auth0 will display that name across all applications in the tenant, creating the illusion of a routing error.

SOLUTION:

To fix this and stop the Regular Web App’s name from bleeding into your SPA’s login flow, you simply need to update your tenant-level branding.

  1. Go to your Auth0 Dashboard .
  2. In the left-hand menu, click on Settings > General .
  3. Look for the Tenant Name field (sometimes referred to as the Friendly Name).
  4. You will likely see the name of your Regular Web App here. Change it to your overarching Company Name, Organization Name, or Brand Name.
  5. Scroll to the bottom and click Save .

Now, when you trigger the login flow from your SPA, the prompt will correctly read:
"Log in to [Your Company Name] to continue to [SPA]."

Let me know if that was the cause of your issue or not!

Kind Regards,
Nik