Can we use checkSession method to renew the auth0 token?

[dinesh.lawate]

Can we use checkSession method to renew the auh0 token with the following conditions?

1. We don’t have a custom domain.
2. The user has blocked Third Party Cookies.

Is there any other solution to the above problem?
I am using Uniserval Login and I am able to sign in and sign up properly except unable to renew the token.

[mathiasconradt]

Just putting this additional information here for others for reference, describing a bit the background of the issue.
I don’t have a solution at hand given the above limitations, other than doing a regular redirect again (even though no user interaction required).

---

Background information on third-party cookies and checkSession:

Troubleshoot Renew Tokens When Using Safari

Why are third party cookies required for checkSession?

After following up with our support team they were able to break it down clearly: Normally auth0.js runs on your domain e.g. contoso.com which is different from the auth0.com domain. So the iframe is created in your app and calling auth0.com which sets a a cookie that’s considered as a third party cookie. Please let me know if this helps clear things up, thanks!

Why does checkSession need cookies?

When a user authenticates, a cookie is stored with the session details. This enables [checkSession] (Auth0.js v9 Reference) to acquire a new token from Auth0 for a user who is already authenticated against Auth0 for your domain. For the [silent authentication] (Single Sign-On) to be possible, you must [Have a SSO cookie for the tenant’s domain (in other words, the user has previously signed in and their saved cookie is still valid);] (Single Sign-On). There have been internal discussions around…

[dinesh.lawate]

Hi @mathiasconradt,

When I checked network request and I found that when I allow 3rd Party Cookies setting then cookies are automatically getting attached to auth0 HTTP request and checkSession succedes but If I disable it then checkSession fails because cookies are not attached to http request. I also checked SSO setting at the tenant level and it is fine.

Is there any workaround for the above problem without using a custom domain or forcing the user to enable 3rd Party cookies?

I hope there must be something that we can do to resolve this issue.

[mathiasconradt]

[…] other than doing a regular redirect again (even though no user interaction required).

This isn’t an option?