Error "At Least One Database, Enterprise or Social Connection Needs to Be Available" When Using Lock

Users encounter an error when logging in, even if the application has connections enabled.

At least one database, enterprise or social connection needs to be available

This issue typically affects the Lock SDK.

• Lock SDK
• Classic Universal Login
• Applications with more than 50 database connections

The Lock SDK has a limitation of 50 database connections enabled per client. If the application has more than 50 database connections enabled, and the connection requested in the /authorize call is not found within the first 50 connections returned by the Lock lookup, this error occurs.

The Lock SDK allows a maximum of 50 database connections per application. For more information, refer to Multi-tenant apps best practices.

To resolve this issue, consider one of the following workarounds:

• Migrate to the New Universal Login Experience, which does not have this limitation.

• Use a different SDK, such as Auth0.js, to build a custom User Interface (UI) for the Classic Universal Login page.

NOTE: This limitation is only present within the Lock SDK.