Dynamic Enterprice connection name to use Authorize on Custom login page

Get Help
,
1

How can we securely determine and trigger the correct enterprise connection (like Okta) on the custom login page based on the user’s email, considering:

  • Rules are deprecated and there are no pre-login triggers available now
  • Actions only run post-login, which doesn’t help for dynamic connection routing
  • The user’s email domain doesn’t directly match the connection name (e.g., vinay@gmail.com → tailorbird_okta)
  • Using Management API from frontend is insecure due to token exposure

Is there any recommended Auth0 pattern or workaround for securely resolving the connection name before calling authorize()?

3

Hi @vinay3

Welcome to the Auth0 Community!

As you mentioned, there’s no recommended pattern for doing it from a public application, like an SPA or a Native application. I encourage you to open a new thread in the Product Feedback category to explain your use case. <ake sure to upvote it to get as many votes as possible and attract as many community members as possible.

Thanks
Dawid

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.