# Potential Impact of Chrome Disabling Third-Party Cookies on Auth0 Functionality

**URL:** <https://community.auth0.com/t/potential-impact-of-chrome-disabling-third-party-cookies-on-auth0-functionality/135576>\
**Category:** Get Help\
**Tags:** google-social-connection, connections\
**Created:** [June 4, 2024, 7:33am UTC](https://community.auth0.com/t/potential-impact-of-chrome-disabling-third-party-cookies-on-auth0-functionality/135576 "2024-06-04T07:33:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arie26](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@arie26](https://community.auth0.com/u/arie26)\
**Post date:** [June 4, 2024, 7:33am UTC](https://community.auth0.com/t/potential-impact-of-chrome-disabling-third-party-cookies-on-auth0-functionality/135576/1 "2024-06-04T07:33:26Z")

</div>

Hi there,

I’m reaching out to inquire about the potential impact of Chrome’s upcoming changes regarding third-party cookies on Auth0’s functionality. As you may be aware, Chrome is planning to disable third-party cookies by default in the coming months.

My understanding is that Auth0 utilizes cookies for certain functionalities. For instance, if I open a new page in a separate tab while allowing cookies, everything works as expected. However, if cookies are restricted, I’m redirected back to the default page.

Could you please clarify how these changes might affect Auth0 and if there are any recommended configurations or workarounds to ensure continued functionality?

Thank you for your time and assistance.

---

<div class="post-metadata">

**Author:** ![marcelina.barycka](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/marcelina.barycka/32/56162_2.png) [@marcelina.barycka](https://community.auth0.com/u/marcelina.barycka)\
**Post date:** [June 4, 2024, 10:05am UTC](https://community.auth0.com/t/potential-impact-of-chrome-disabling-third-party-cookies-on-auth0-functionality/135576/2 "2024-06-04T10:05:28Z")

</div>

Hey there @arie26 ,

From my side, happy to start with the known workarounds -

1. Do not rely on [silent authentication](https://auth0.github.io/auth0-spa-js/classes/Auth0Client.html#getTokenSilently) (cookies-based) if your applications and Auth0 tenant _don’t share_ the same second-level domain.

2. In the above scenario, leverage refresh token rotation instead (a common authentication and authorization pattern for SPAs). More [here](https://community.auth0.com/t/how-do-i-use-refresh-tokens-in-a-spa/135558) 🙂

---

<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:** [June 24, 2024, 1:54pm UTC](https://community.auth0.com/t/potential-impact-of-chrome-disabling-third-party-cookies-on-auth0-functionality/135576/4 "2024-06-24T13:54:42Z")

</div>

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