Auth0 strongly recommends that authentication transactions be handled via Universal Login. Doing so offers the easiest and most secure way to authenticate users. However, some situations may require that authentication forms be directly embedded in an application. Although not recommended, cross-origin authentication provides a way to do this.
What is cross-origin authentication?
When authentication requests are made from your application (via the Lock widget or a custom login form) to Auth0, the user's credentials are sent to a domain which differs from the one that serves your application. Collecting user credentials in an application served from one origin and then sending them to another origin can present certain security vulnerabilities, including the possibility of a phishing attack.
Auth0 provides a cross-origin authentication flow which makes use of third-party cookies. The use of third-party cookies allows Lock and Auth0's backend to perform the necessary checks to allow for secure authentication transactions across different origins. This helps to prevent phishing when creating a Single Sign-on experience with the Lock widget or a custom login form in your application and it also helps to create a secure login experience even if SSO is not the goal.
Cross-origin authentication is not recommended and is only necessary when authenticating against a directory using a username and password. Social IdPs and enterprise federation use a different mechanism, redirecting via standard protocols like OpenID Connect and SAML. Additionally, cross-origin authentication is only applicable to embedded login on the web (using Lock or auth0.js). Native applications using embedded login make use of the standard OAuth 2.0 Token endpoint.
Because cross-origin authentication is achieved using third-party cookies, disabling third-party cookies will make cross-origin authentication fail. Some browsers, such as the newest version of Firefox, disable third-party cookies by default, meaning that cross-origin authentication will not work for users on Firefox. The only way to make embedded login work for Firefox users is to use a custom domain, as described below.
There are two approaches you can follow to remediate the issue:
Enable a Custom Domain on your tenant and host your web application in a domain that has the same top-level domain as your Auth0 custom domain. For example, you host an application at
https://northwind.comand set your Auth0 custom domain as
https://login.northwind.com. This way the cookies are no longer third-party (because both your Auth0 tenant and your application are using the same top-level domain), and thus, are not blocked by browsers.
Provide a cross-origin verification page that will make cross-origin authentication work in a limited number of browsers even with third-party cookies disabled (see the browser testing information below).
These issues are another reason why the more practical solution is to use Universal Login.
Configure your application for cross-origin authentication
Ensure that the Allowed Web Origins field in the Application Settings is set to the domain making the request. The URLs specified for Allowed Web Origins can contain wildcards for subdomains and cannot contain relative paths after the domain.
If you don't enable Custom Domains, you will need to create a page that uses auth0.js to act as a fallback for the cross-origin transaction. More information on setting up this page is provided below.
Create a cross-origin verification page
There are some cases when third-party cookies will not be available. Certain browser versions do not support third-party cookies and, if they do, there will be times that they will be disabled in a user's settings. You can use auth0.js in your application on a dedicated page to properly handle cases when third-party cookies are disabled. This page must be served over SSL.
crossOriginVerification as a fallback will only work if the browser is on the support matrix as Yes under Third-Party Cookies Disabled. For some browsers, such as Chrome, Opera, and Safari, when third-party cookies are disabled, cross-origin authentication will not work at all unless you enable Custom Domains.
Provide a page in your application which instantiates
WebAuth from auth0.js. Call
crossOriginVerification immediately. The name of the page is at your discretion.
to configure this snippet with your account
When third party cookies are not available, auth0.js renders an
iframe to call a different cross-origin verification flow.
Add the URL of this callback page to the Cross-Origin Verification Fallback field in your Application's settings in the Dashboard, under the Advanced > OAuth panel.
For production environments, verify that the Location URL for the page does not point to localhost.
See the cross-origin auth sample for more information.
Error Codes and Descriptions
When Auth0.js v9 (and Lock v11) is used for embedded login, it employs the
/co/authenticate endpoint, which has the following errors.
||Invalid request body. All and only of client_id, credential_type, username, otp, realm are required.|
||Cross origin login not allowed.|
||Unknown credential type parameter.|
||Unknown realm non-existent-connection.|
||Wrong email or password.|
||This login attempt has been blocked because the password you're using was previously disclosed through a data breach (not in this application).|
||Your account has been blocked after multiple consecutive login attempts. We’ve sent you an email with instructions on how to unblock it.|
||We have detected suspicious login behavior and further attempts will be blocked. Please contact the administrator.|
In addition, you can also get a generic 403 error without an
error_description property. The response body would just include something similar to the following:
Origin https://test.app is not allowed.
Browser testing support
The following browsers can use cross-origin authentication when third-party cookies are disabled:
Microsoft Internet Explorer
Samesite Cookie Attributes
Previously in Auth0, the
samesite cookie attribute options were
lax. If you didn't set the attribute manually, Auth0 would use the default value of
Effective February 2020, Google Chrome v80 will change the way it handles cookies. To that end, Auth0 plans on implementing the following changes to how it handles cookies:
Cookies without the
samesiteattribute set will be set to
sameSite=nonemust be secured, otherwise they cannot be saved in the browser's cookie jar
The goal of these changes are to improve security and help mitigate CSRF attacks.