Ready to post? First try searching for your answer.Hi all,
Following up on this thread:
I tried the “re-create the connections” approach described above, and I was able to confirm that it works as expected for reordering connections within the same category.
While testing further, a question came up about the internal behavior that I’d like to confirm.
The social buttons actually belong to different connection types under the hood:
Google → Social connection
LINE → Social connection
Facebook → Social connection
Microsoft Account → Enterprise connection (Azure AD / waad)
Both the LINE and Facebook connections were created after the Microsoft Account (waad) connection. If button order were based purely on creation date regardless of connection type, I’d expect Microsoft Account to appear above LINE and Facebook. However, on the actual login screen, LINE and Facebook are displayed above Microsoft Account.
This leads me to think that connections aren’t being sorted on a single global creation-date timeline. Rather, it looks like Social connections are grouped together and rendered before Enterprise connections, with creation date only determining the order within each group.
I’d like to confirm whether this understanding is correct — i.e., that connections are grouped by category (Social before Enterprise), and creation date only determines the order within each group.
If anyone from the Auth0 team or anyone who has verified this themselves could weigh in, that would be very helpful.
You are asking whether Auth0 New Universal Login orders login buttons by grouping Social connections before Enterprise connections and then applying creation date only within each group. Currently, there is no relevant Auth0 documentation, support article, or community post that I can reference which confirms this internal ordering behavior.
In the New Universal Login experience, Auth0 DOES groups connections by category—Social connections always render above Enterprise connections. The chronological creation date sorting only applies within those specific groupings.
To reiterate the mechanics under the hood: when the login widget is rendered, Auth0 splits your enabled connections into distinct internal arrays based on their underlying strategy:
Social Array: Handled first (e.g., google-oauth2, line, facebook).
Enterprise Array: Handled second (e.g., waad, saml, okta), assuming they are configured to “Display connection as a button.”
Because the widget iterates through the Social array completely before moving to the Enterprise array, it is practically impossible for an Enterprise button to appear above a Social button natively, regardless of which one was created first in your tenant.
If this strict categorical grouping is a dealbreaker for your application’s user experience, you have two main workarounds:
Use Identifier-First Login (Home Realm Discovery): Turn off the “Display connection as a button” toggle for Microsoft Entra ID. The login screen will only show your Social buttons and an email input. When corporate users type their @company.com email, Auth0 will instantly redirect them to the Microsoft login, keeping the UI incredibly clean.
Use Advanced Customizations (ACUL): If you absolutely need all of them as buttons in a specific, interleaved order, you will need to build a custom login page using the @auth0/auth0-acul-js SDK, which allows you to manually sort the connections array and render the UI however you see fit.
First try searching for your answer.Hi all,