Auth0 Home Blog Docs

Why are third party cookies required for checkSession?



Can anyone can elaborate on why third-party cookies are required for the checkSession call in auth0.js per

My understanding is that checkSession works by creating a hidden iframe with src as the Auth0 subdomain (e.g. and then passes any tokens back to the app via postMessage. In this case, the only cookies should be first party cookies that the Auth0 subdomain ( sets on itself since it communicates to the app via postMessage.

I looked in the source and also didn’t see any references to setting cross-domain cookies, but I obviously could have missed something (or the requirement could be from some code on the Auth0 side outside of auth0.js)


Hey there @ncknuna, let me see if I can find you more details on this subject.Thanks.


After following up with our support team they were able to break it down clearly:

Normally auth0.js runs on your domain e.g. which is different from the domain. So the iframe is created in your app and calling which sets a a cookie that’s considered as a third party cookie.

Please let me know if this helps clear things up, thanks!


Hey James,

Thanks for the quick followup; that makes sense. In retrospect, I realize that my understanding of what “third-party cookies” were was wrong, and I had assumed that they were cookies that one domain was trying to set on a different domain (slightly connected to a cross-origin request with withCredentials set). Now that I understand that third-party cookies are just any cookies set by child iframes with a different domain, the documentation makes a lot more sense. Thanks!


I’m glad we could help @ncknuna, let us know in the future if you have any additional questions and have a happy holidays!


Thanks James! Happy holidays to you too!