Feature: Enabling Multiple Database Connections for a Single Application
Description: Address the limitations around using multiple database connections within a single application. Although this is currently documented as a “solution,” it appears to function more as a workaround for an underlying issue rather than a true resolution. The responsibility for handling this behavior is effectively shifted to the customer, rather than being natively supported.
Use case: A single application serving multiple organizations, each with its own user database to support isolation and streamlined onboarding. This should be fully supported through Universal Login. If the same scenario can be handled in a custom login page, Universal Login should be capable of supporting it as well. Otherwise, it undermines the intent of a “universal” login if it requires additional patching to work with a documented and supported authentication architecture.