Here’s an example of what I am currently experiencing.
I have created multiple tenants in the following order:
tenantFoo
tenantBar
tenantBaz
Then I created an app applicationBar in tenant tenantBar. The configuration for this looks something like this:
Name: applicationBar
Domain: tenantBar.eu.auth0[dot]com
ClientID: clientId123Bar
The application is also listed Menu → Applications → Applications when tenantBar is the selected tenant. So far so good, this is exactly what I would expect.
Shortly after creating the application, when I refresh the list of applications the application will be gone and can now be found in tenantFoo and will have the following configuration:
Name: applicationBar
Domain: tenantFoo.eu.auth0[dot]com
ClientID: clientId123Bar
What am I missing here? I would expect an application to be assigned to a single tenant and to be immovable.
In my client-side Angular code I was using the following configuration:
{
domain: 'tenantBar.eu.auth0[dot]com',
clientId: 'clientId123Bar'
}
When redirecting the user to the Universal Login using the initial domain (tenantBar.eu.auth0[dot]com) I will get the following error message:
**invalid_request** : The client with id: "clientId123Bar" (tenantBar) was not found
If I change the configuration to this, it works again:
{
domain: 'tenantFoo.eu.auth0[dot]com',
clientId: 'clientId123Bar'
}