Hello Auth0 community, I’ll state my question first, and then provide detail below:
Question: is it possible and work-able to support >1 (e.g. 2) hosted login pages (HLPs) with custom UIs within one Auth0 tenant? IOW:
a. is it possible to deploy / host 2 distinct HLPs, each with their own set of (custom) HTML/CSS/JS in one Auth0 tenant?
b. if yes to “a”, is it possible for >1 applications to distinguish between these 2 HLPs, such that appA uses HLP-A, and appB uses HLP-B?
Detail: based on this table in Auth0’s documentation (https://auth0.com/docs/libraries/when-to-use-lock), we created an HLP with a custom UI. This HLP handles multiple database connections (we can for example support users authenticating with username-based accounts, and email address-based & social accounts). We call these different behaviors ‘modes’ within our HLP. Also of course, our HLP matches our company branding and does not look like Auth0’s ‘Lock’ or (new) Universal login experience.
We have found that maintaining these different ‘modes’ is challenging from a code & testing point of view. Conceptually it seems like a really cool idea if we could separate these modes into 2 distinct HLPs (i.e. 2 distinct web SPAs):
- HLP that supports our ‘old user accounts’ (i.e. username-based users)
- HLP that supports our ‘newer user accounts’ (i.e. email & social based users)
Over time we are transitioning our username-based users to email, but we have choosen to transition our users in waves so to speak.
So again the core questions:
Q1: is this possible to do from a deployment point of view (e.g. using the auth0-deploy-cli + Auth0 Management API)?
Q2: if yes to ‘Q1’, is it possible for our applications (e.g. web SPAs & native mobile apps) to ‘distinquish’ which HLP a user should be redirected to?
Or, are we barking up the wrong tree with this idea?