Native Per-User Connection Routing or SDK Support for Dynamic Connections

Product Feedback
, , , ,
1

Feature: Native Per-User Connection Routing or SDK Support for Dynamic Connections

Description: Currently, the New Universal Login does not support routing users to different connection types (such as switching between Database/Password and Passwordless/OTP) based on their identifier. While this routing is possible by manually passing a connection parameter from the client-side to the /authorize endpoint or the React SDK, the ACUL SDK itself is rigid and cannot update the connection context once the transaction starts, which does not allow logic centralization for this routing.

I thought about 2 possible solutions:

  1. Per-User Routing: Auth0 should natively resolve the connection type based on the user identifier/profile during the Identifier-First flow, eliminating the need for client-side logic.

  2. SDK Flexibility: Allow the ACUL LoginId.login() method to accept a connection parameter to override the transaction target dynamically after a lookup.

Use-case: We are building a high-scale B2B application where different users within the same organization, application, or email domain require different authentication methods (based on their role, for example). Currently, we are forced to abandon the native Auth0 hosted experience and build custom “Identifier-First” screens in all of our React and Mobile apps to handle this routing. Implementing native per-user routing would allow us to leverage the security of Universal Login while providing the identity orchestration flexibility required for enterprise-grade migrations and mixed-auth environments.