# Disabling 3rd party cookies breaks MFA

**URL:** <https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530>\
**Category:** Get Help\
**Created:** [June 22, 2018, 10:27pm UTC](https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530 "2018-06-22T22:27:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alex555](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/alex555/32/8301_2.png) [@alex555](https://community.auth0.com/u/alex555)\
**Post date:** [June 22, 2018, 10:27pm UTC](https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530/1 "2018-06-22T22:27:16Z")

</div>

When I disable 3rd party cookies (eg - turning on “Block third-party cookies” in Chrome), then the MFA screen for my app shows a red banner with “WE CANNOT CONNECT TO REAL TIME CHANNEL.”

This issue persists even after clearing my cookies as suggested in [this topic](http://community.auth0.com/t/mfa-failing-we-cannot-connect-to-real-time-channel/11250), which isn’t surprising since the [auth0 cross origin authentication](https://auth0.com/docs/cross-origin-authentication) article explicitly states “disabling third-party cookies will make cross-origin authentication fail”.

However that same articles suggests using a custom domain to fix the problem - which is what my app is currently using. I have an app that lives at `mySubdomain.myCustomApp.com`, and I’ve enabled a custom login domain at `login.myCustomApp.com`.

Does my custom domain need to point to `login.mySubdomain.myCustomApp.com` to be considered a first party cookie?

---

<div class="post-metadata">

**Author:** ![Thornton](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@Thornton](https://community.auth0.com/u/Thornton)\
**Post date:** [October 5, 2018, 12:20am UTC](https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530/2 "2018-10-05T00:20:55Z")

</div>

Did you ever solve this? We have the same problem.

Block 3. Party cookies + custom domain = Mfa error  
But:  
Block 3. Party cookies + NO custom domain = no error

---

<div class="post-metadata">

**Author:** ![alex555](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/alex555/32/8301_2.png) [@alex555](https://community.auth0.com/u/alex555)\
**Post date:** [October 5, 2018, 2:24pm UTC](https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530/3 "2018-10-05T14:24:36Z")

</div>

Yes, we finally did! While emailing with auth0 customer support, they suggested changing this line on the hosted login page:

```auto
{% if stateCheckingMechanism %}stateCheckingMechanism: "{{ stateCheckingMechanism }}", {% endif %}

```

to

```auto
stateCheckingMechanism: "polling",

```

which fixed the issue for us.

---

<div class="post-metadata">

**Author:** ![Thornton](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@Thornton](https://community.auth0.com/u/Thornton)\
**Post date:** [October 5, 2018, 2:40pm UTC](https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530/4 "2018-10-05T14:40:53Z")

</div>

OK. Interesting.  
I actually fixed ours by changing:  
" mfaServerUrl: “{{ mfaServerUrl }}”,"  
to  
"mfaServerUrl: “[https://login.ourdomain.com/guardian/”](https://login.ourdomain.com/guardian/%E2%80%9D) in the Multifactor hosted page.

But im pretty sure that is a hack?

---

<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:** [July 26, 2019, 1:12pm UTC](https://community.auth0.com/t/disabling-3rd-party-cookies-breaks-mfa/12530/5 "2019-07-26T13:12:31Z")

</div>

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