Auth0 LDAP Connection Button Does Not Appear on Login Page

An Active Directory / Lightweight Directory Access Protocol (LDAP) enterprise connection does not display a login button on the Auth0 Universal Login page because it is not a federated connection. The observable issue occurs when an administrator enables an LDAP connection for an application, but the LDAP login button fails to render on the login prompt.

• Auth0
• Enterprise Connections
• Active Directory / LDAP

Active Directory / LDAP connections are not federated connections. Auth0 collects passwords for these connections directly in the user interface, similar to standard database connections. Therefore, Auth0 does not have a native login button for LDAP connections.

How is the missing LDAP connection button resolved?

There are 2 known possible methods to work around the missing LDAP connection button.

Pass the connection parameter from the application to Auth0

Implement selection logic within the application by creating separate login buttons and passing the connection parameter to the authorize endpoint.

1. Create separate login buttons within the application interface, such as Login with LDAP and Login with Auth0.
2. Configure the application to pass a connection parameter when communicating with the Auth0 /authorize endpoint. The specific parameter on this API can be seen in the Authorize documentation.
3. Specify the exact connection name in the parameter to restrict the login flow to that specific connection.

Implement a two-tenant architecture to generate a login button

Create a secondary Auth0 tenant to act as an identity provider and connect it to the primary tenant using an enterprise connection.

1. Create a separate Auth0 tenant.
2. Configure the new tenant to connect to the LDAP server using the Active Directory/LDAP connector.
3. Navigate to the original primary tenant.
4. Connect the primary tenant to the new secondary tenant using an Enterprise connection, such as OpenID Connect (OIDC) or Security Assertion Markup Language (SAML).
5. Enable the new Enterprise connection for the target application to generate a native login button on the Universal Login page.