# VueJS: Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox **URL:** \ **Category:** Get Help\ **Tags:** login-experience, new-universal-login-experience\ **Created:** [June 22, 2024, 2:08pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849 "2024-06-22T14:08:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![patrickbeck91](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/patrickbeck91/32/53958_2.png) [@patrickbeck91](https://community.auth0.com/u/patrickbeck91)\ **Post date:** [June 22, 2024, 2:08pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849/1 "2024-06-22T14:08:56Z")
Hey, I’m currently wondering about this message in my Google Chrome Console: “Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.” How I can prevent this issue in the future? Will there be an update for the VueJS SDK or something? ---
**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\ **Post date:** [June 25, 2024, 3:32pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849/2 "2024-06-25T15:32:26Z")
Hey there @patrickbeck91 > [@patrickbeck91](#): > > How I can prevent this issue in the future? Will there be an update for the VueJS SDK or something? Please see the following post: > [@Third-party cookie deprecation in Chrome](https://community.auth0.com/t/third-party-cookie-deprecation-in-chrome/122836/6): > > Sorry, let me re-phrase my answer as using a custom domain is just the most straightforward solution, but not the only one. Any tenant that does not have the ability to utilize a custom domain can get around third-party cookie issues by using [refresh tokens](https://auth0.com/docs/secure/tokens/refresh-tokens) / [refresh token rotation](https://auth0.com/docs/secure/tokens/refresh-tokens/refresh-token-rotation). This is preferred to traditional [silent auth](https://auth0.com/docs/authenticate/login/configure-silent-authentication) which does rely on an auth0 cookie (third-party without a custom domain). ---
**Author:** ![patrickbeck91](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/patrickbeck91/32/53958_2.png) [@patrickbeck91](https://community.auth0.com/u/patrickbeck91)\ **Post date:** [June 26, 2024, 12:28pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849/4 "2024-06-26T12:28:26Z")
Does not help me very well… can’t you just adjust the examples so this is no problem in the future? As you see I’m not the only one. I downloaded the current example and get the same messages. ---
**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\ **Post date:** [June 26, 2024, 5:42pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849/5 "2024-06-26T17:42:46Z")
The examples may be updated at some point as adjusting to Chrome’s Privacy Sandbox is still a work in progress - That being said adding a custom domain (which mitigates 3rd party cookies entirely) is an option only on paid plans currently and the use of refresh tokens is encouraged but not required. ---
**Author:** ![jeffrey597doss](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffrey597doss/32/58066_2.png) [@jeffrey597doss](https://community.auth0.com/u/jeffrey597doss)\ **Post date:** [June 26, 2024, 7:40pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849/6 "2024-06-26T19:40:52Z")
Hello! To address the upcoming blocking of third-party cookies in Chrome and similar browsers, take proactive steps in your VueJS application. Ensure cookies are set with the appropriate same-site attributes (Lax or Strict) to maintain functionality across domains. Shift towards using first-party contexts for cookie operations within your application’s domain rather than relying on third-party cookies. Stay updated with VueJS community discussions and potential library updates that may provide enhanced cookie management strategies aligned with evolving browser privacy policies. These measures will help mitigate potential disruptions caused by future browser updates regarding third-party cookie handling. ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [July 10, 2024, 7:41pm UTC](https://community.auth0.com/t/vuejs-third-party-cookie-will-be-blocked-in-future-chrome-versions-as-part-of-privacy-sandbox/136849/7 "2024-07-10T19:41:25Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.