Skip to content

chore: rebalance embedded login messaging and add hybrid-use framing#1327

Open
tomauth0 wants to merge 13 commits into
auth0:mainfrom
tomauth0:embedded-cleanup
Open

chore: rebalance embedded login messaging and add hybrid-use framing#1327
tomauth0 wants to merge 13 commits into
auth0:mainfrom
tomauth0:embedded-cleanup

Conversation

@tomauth0

@tomauth0 tomauth0 commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Description

Remove anti-embedded language across embedded-login, universal-vs-embedded-login,
cross-origin-authentication, native-login, passwordless best practices,
lock/auth0js, and the brute-force playbook. Reframe trade-offs as architectural
choices and clarify that Universal Login and Embedded Login are not mutually
exclusive — the same app can use UL for primary sign-in plus embedded flows for
factor enrollment, step-up, passkey registration, or account linking.

Checklist

  • I've read and followed CONTRIBUTING.md.
  • I've tested the site build for this change locally.
  • I've made appropriate docs updates for any code or config changes.
  • I've coordinated with the Product Docs and/or Docs Management team about non-trivial changes.

@tomauth0 tomauth0 requested a review from a team as a code owner June 2, 2026 13:38
## Browser considerations

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 <Tooltip tip="Custom Domain: Third-party domain with a specialized, or vanity, name." cta="View Glossary" href="/docs/glossary?term=custom+domain">custom domain</Tooltip>, as described below.
Modern browsers (including Firefox, Safari with ITP, and Chromium-based browsers) restrict or block third-party cookies by default for privacy reasons. Web applications relying on third-party cookies for cross-origin authentication may fail in those browsers. To make embedded login work reliably across browsers, configure your tenant so the application and Auth0 share a top-level domain. This is also considered a security best practice.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The best security practice might be confusing here. Maybe we can edit the last sentence to be something like:
Also, as a security best practice, we recommend using a custom domain or multiple custom domains with the same top-level domain.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated the wording here to hopefully be clearer

Comment thread main/docs/authenticate/login/universal-vs-embedded-login.mdx Outdated
Comment thread main/docs/authenticate/login/universal-vs-embedded-login.mdx Outdated
tomauth0 and others added 13 commits June 12, 2026 11:17
  Remove anti-embedded language across embedded-login, universal-vs-embedded-login,
  cross-origin-authentication, native-login, passwordless best practices,
  lock/auth0js, and the brute-force playbook. Reframe trade-offs as architectural
  choices and clarify that Universal Login and Embedded Login are not mutually
  exclusive — the same app can use UL for primary sign-in plus embedded flows for
  factor enrollment, step-up, passkey registration, or account linking.
Co-authored-by: Amanda VS <amanda.vanscoy@auth0.com>
Co-authored-by: Amanda VS <amanda.vanscoy@auth0.com>
  Remove anti-embedded language across embedded-login, universal-vs-embedded-login,
  cross-origin-authentication, native-login, passwordless best practices,
  lock/auth0js, and the brute-force playbook. Reframe trade-offs as architectural
  choices and clarify that Universal Login and Embedded Login are not mutually
  exclusive — the same app can use UL for primary sign-in plus embedded flows for
  factor enrollment, step-up, passkey registration, or account linking.
Co-authored-by: Amanda VS <amanda.vanscoy@auth0.com>
Co-authored-by: Amanda VS <amanda.vanscoy@auth0.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants