Third party cookies are being blocked even with Custom Domain

Users are experiencing issues when clicking links from emails that were sent to them. The issue stems from browsers blocking third party cookies, blocking the app from authenticating them. This happens even though we have custom domain set up in our tenant. From my understanding, especially from reading through the forums, our custom domain should be the solution.

Please assist as soon as possible, as we have been receiving complaints from users multiple times per day saying that links in emails have not been working. Please see browser console log below.

Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, reading third-party cookies will be blocked. This behavior protects user data from cross-site tracking.
Please refer to the article linked to learn more about preparing your site to avoid potential breakage.
1 cookie
Name	Domain & Path
auth0.ssodata	app.example.com/

Hi @perryraskin,

Welcome back to the Auth0 Community!

In order for the custom domain to help getting around the block of 3rd party cookies on browsers that prevent using them lately, it has to be configured on a subdomain of the application’s website domain. For example, if your application is hosted on example.com , the custom domain would need to be of the format subdomain.example.com .

You can also check out this knowledge article - Chrome Phasing Off Third-Party Support Cookies.

Our documentation on the matter also suggests :

Recent advancements in user privacy controls in browsers adversely impact the user experience by preventing access to third-party cookies. You can use Refresh Token Rotation as an alternative that provides a secure method for using refresh tokens in SPAs while providing end-users with seamless access to resources without the disruption in UX caused by browser privacy technology like ITP.

A large discussion about it was already made under this community post as well - Another post regarding Third-party cookie deprecation in Chrome.

Hope this helps this case, but others as well!
Thanks,
Remus

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