# Auth0 Failed Silent Auth on Safari/iOS Chrome Mobile with Rotational Refresh Tokens ON and Custom Domains ON

**URL:** <https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032>\
**Category:** Get Help\
**Tags:** auth0, login\
**Created:** [October 8, 2021, 7:56pm UTC](https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032 "2021-10-08T19:56:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![han1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/han1/32/13039_2.png) [@han1](https://community.auth0.com/u/han1)\
**Post date:** [October 8, 2021, 7:56pm UTC](https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032/1 "2021-10-08T19:56:12Z")

</div>

Hi tere,

Here is the situation:

**This works:**  
I have setup my production site(eg: `www.production.com`) with the custom domain like `auth.production.com` at Auth0 dashboard. After authorizing from Auth0 it goes back to `www.production.com` successfully on all browsers and iOS devices.

**This doesn’t work**  
However, when I test Auth0 Universal Login on my staging domain(eg: `www.staging.com`) this doesn’t work at all.

Before this post, I have tried all relevant solutions:

1 Set up **rotational refresh tokens** and use `useRefreshTokens={true}` and `cacheLocation="localstorage"` in my latest Auth0 React SDK `"@auth0/auth0-react": "^1.8.0"`.

> See in this link `community.auth0.com/t/silent-authorization-not-working-after-login-signup/37114`

2 Double checked on **Refresh Token Rotation**

> **[Refresh Token Rotation](https://auth0.com/docs/secure/tokens/refresh-tokens/refresh-token-rotation)**
>
> Describes how refresh token rotation provides greater security by issuing a new refresh token with each request made to Auth0 for a new access token by a client using refresh tokens.

3 Went through **Troubleshoot Renew Tokens When Using Safari**

> **[Troubleshoot Renew Tokens When Using Safari](https://auth0.com/docs/troubleshoot/authentication-issues/renew-tokens-when-using-safari)**
>
> Issues with token renewal in Safari when ITP is enabled.

> **[Configure Cross-Origin Resource Sharing](https://auth0.com/docs/get-started/applications/set-up-cors)**
>
> Describes how to configure Cross-Origin Resource Sharing (CORS) for an Auth0-registered application using the Auth0 Dashboard.

I made sure when I turned off **Prevent cross-site tracking** my staging domain worked.

So, after all that, can you please give me some directions on `develop` and `staging` envs solutions? What if those domains are all separate without sharing the same parent domain?

Do I have to purchase another tenant for different envs? I’m afraid that this is going to make the development process very complicated as I have to do data transition a lot!

Or, can I have multiple custom domains for all my different envs?

Thanks!

---

<div class="post-metadata">

**Author:** ![han1](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/han1/32/13039_2.png) [@han1](https://community.auth0.com/u/han1)\
**Post date:** [October 8, 2021, 8:21pm UTC](https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032/2 "2021-10-08T20:21:42Z")

</div>

I think I found out the root cause:

> When you call getAccessTokenSilently are you using the same audience and scope that is set in the Auth0Provider? I’ve seen in some cases that silent auth will be required because a new scope or audience is requested after the app initiates. Silent …

> [@Getting Silent Auth working on Safari/iOS with RefreshTokens and cacheLocation localstorage](https://community.auth0.com/t/getting-silent-auth-working-on-safari-ios-with-refreshtokens-and-cachelocation-localstorage/61059):
>
> Which SDK this is regarding: e.g. @auth0/auth0-react SDK Version: 1.1.0 Platform Version: React 16.13.1 Code Snippets/Error Messages/Supporting Details/Screenshots: Unhandled Promise Rejection: Error: Login required Hi, I’ve been using the free tier of auth0 to authenticate my application I’m developing with my team and I cannot for the life of me figure out how to get silentAuthentication working on Safari for macOS and iOS with regards to the Intelligent Tracking Prevention (ITP). Link…

By the way, this is definitely a new thing, as earlier this year all above worked, but somehow recently I found out we will need to pass in exact both `scope` and `audience` to `Auth0Provider`.

Can can I track those software updates by the way?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [October 23, 2021, 8:22pm UTC](https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032/3 "2021-10-23T20:22:31Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [June 12, 2025, 5:22pm UTC](https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032/4 "2025-06-12T17:22:31Z")

</div>

Hi team! 👋

This is a heads-up that we’re hosting an [Ask Me Anything (AMA) session 📢 on our new Multiple Custom Domains (MCD) capability](https://community.auth0.com/t/june-25-auth0-community-ask-me-anything-multiple-custom-domains/187776). Our Platform Infrastructure Product Manager, Pawan Bhardwaj, will be live on **June 25, 2025, from 9 AM to 11 AM PST** 🗓 to answer all your questions—from high-level strategy to specific technical implementation.

You can submit your questions from **now until June 24** ✏, and we’ll provide detailed written answers during the live event.

If you have any questions about managing multiple brands 🏢, creating tailored login experiences 🎨, or simplifying your architecture with a single tenant ⚙, feel free to drop them in [this thread](https://community.auth0.com/t/june-25-auth0-community-ask-me-anything-multiple-custom-domains/187776). We look forward to your questions and seeing you there!

[June 25 Auth0 Community Ask Me Anything: Multiple Custom Domains](https://community.auth0.com/t/june-25-auth0-community-ask-me-anything-multiple-custom-domains/187776)

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [July 30, 2025, 10:16am UTC](https://community.auth0.com/t/auth0-failed-silent-auth-on-safari-ios-chrome-mobile-with-rotational-refresh-tokens-on-and-custom-domains-on/71032/5 "2025-07-30T10:16:44Z")

</div>

Hi everyone! 👋

**Multiple Custom Domains (MCD)** support in a single tenant is now available in **Early Access (EA)**, only for Enterprise customers. This capability lets you:

- 🔑 Securely manage multiple branded domains under one Auth0 tenant
- 🚀 Improve user trust with seamless, white‑labeled login experiences
- 🛡 Host customer‑specific domains to meet data residency and regulatory requirements

To learn more, check out the detailed documentation:  
[https://auth0.com/docs/customize/custom-domains/multiple-custom-domains](https://auth0.com/docs/customize/custom-domains/multiple-custom-domains)

For detailed use cases and best practices, explore our guides here:

- Use Cases: [https://auth0.com/docs/customize/custom-domains/multiple-custom-domains/mcd-use-cases](https://auth0.com/docs/customize/custom-domains/multiple-custom-domains/mcd-use-cases)
- Best Practices: [https://auth0.com/docs/customize/custom-domains/multiple-custom-domains/mcd-best-practices](https://auth0.com/docs/customize/custom-domains/multiple-custom-domains/mcd-best-practices)

If you’re interested in using this feature, please contact your Sales Executive or Technical Account Manager or open a support ticket through the Auth0 Support Center.

Thank you for being part of the Auth0 Community! 🎉

Dawid
