# Auth0 client can authenticate to another tenant?

**URL:** <https://community.auth0.com/t/auth0-client-can-authenticate-to-another-tenant/30087>\
**Category:** Get Help\
**Tags:** jwt, access-token, login, auth0\
**Created:** [August 29, 2019, 3:14pm UTC](https://community.auth0.com/t/auth0-client-can-authenticate-to-another-tenant/30087 "2019-08-29T15:14:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ran.ju](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ran.ju/32/12818_2.png) [@ran.ju](https://community.auth0.com/u/ran.ju)\
**Post date:** [August 29, 2019, 3:14pm UTC](https://community.auth0.com/t/auth0-client-can-authenticate-to-another-tenant/30087/1 "2019-08-29T15:14:51Z")

</div>

In my company, we have 3 tenants, one for each environment (dev, stage, prod).

The auth URL for the tenants are like [https://mycompany-dev.eu.auth0.com](https://mycompany-dev.eu.auth0.com), etc.

We just discovered that we can send password grant requests to [https://mycompany-prod.eu.auth0.com](https://mycompany-prod.eu.auth0.com), with a client ID from the dev tenant. How is this possible??? Shouldn’t Auth0 check that there’s no such client ID in the prod tenant, and reject the request?

Decoding the JWT token, we see that `iss` is correctly set to [mycompany-dev.eu.auth0.com](http://mycompany-dev.eu.auth0.com), so it is issued by the correct tenant. So it is just weird that I can use one tenant’s URL to login with another tenant’s client.

Is this a feature of Auth0? Is this behaviour documented anywhere?

---

<div class="post-metadata">

**Author:** ![ieuan.jenkins](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ieuan.jenkins/32/21701_2.png) [@ieuan.jenkins](https://community.auth0.com/u/ieuan.jenkins)\
**Post date:** [June 3, 2020, 12:31pm UTC](https://community.auth0.com/t/auth0-client-can-authenticate-to-another-tenant/30087/2 "2020-06-03T12:31:03Z")

</div>

Sounds like the same issue we’ve encountered here:

> [@Auth0 not respecting multi-tenancy](http://community.auth0.com/t/auth0-not-respecting-multi-tenancy/38870):
>
> Our organisation has two tenants. staging-tenant.eu.auth0.com prod-tenant.eu.auth0.com We are using this to run M2M client credential authentication. In each respective tenant, we have created the relevant M2M apps. For this example, app1 exists in staging-tenant.eu@auth0.com. If I send a token request with the app1 credentials to the prod tenant I get a valid jwt back. curl --request POST \ --url https://prod-tenant.eu.auth0.com \ --header 'content-type: application/json' \ --data '{…
