Hi @pranavijillellamudi
Welcome back to the Auth0 Community!
I am sorry about the delayed response to your questions.
- Can we reuse or adapt Classic UL custom code in ACUL?
No, at least not directly. Since the architectures are quite different from each other, you will be able to lift your CSS and adapt it accordingly to the new HTML architecture of UL, reusing your branding customization and any custom JS logic might need to be re-implemented using Actions.
- What are auth0 universal login templates and prompts..how are they interlinked with acul
A prompt is basically the screen which is being rendered during the login process, such as the Login, Signup, MFA. Each of these prompts have different screens associated with them, which are the different steps which the user can reach during the execution of the specific prompt.
The templates are the underlying code which is used to render the specific prompts.
ACUL is only used to customize these prompts and screens, otherwise, they are a core elements of UL and the authentication flow is the one dictating their sequence.
- How much custom HTML/CSS/JS is actually allowed in ACUL?
CSS → You have full control over the customization.
HTML->Very limited, you will be able to change text, labels, and placeholders for various prompts via the Management API.
JS-> None, client-side JavaScript is not allowed for security reasons. All custom logic must be moved to Auth0 Actions .
- How are Organizations supposed to be handled in ACUL from a UI perspective?
You can customize the specific screens for Organizations depending on the flow you want to implement within your application. The specific prompt should be Organizations, otherwise, their respective login screens should inherit the customizations you have put in place for your login prompts/screens.
- Can ACUL be tested locally (localhost)?
Yes, once you deploy the changes, you will be able to test the login flow and UL should reflect the changes immediately.
- Does acul support only react?
The underlying technology that Auth0 uses to build the New Universal Login pages is React . However, you mainly interact with it using CSS and API calls.
If i click configure screens it is asking me to log in to auth0.com but my tenant is private tenant hosted on auth0app.com.. So i cant login.
The issue you’re facing is because this visual editor is a public cloud tool that is incompatible with your private cloud tenant. You will not be able to use this visual editor. You must manage your UL customizations via the Management API or other IaCs(Auth0 CLI/Terraform/Deploy CLI).
Additionally, you can check out this migration guide from Classing Login to UL with ACUL here.
If you have any other questions, let me know!
Kind Regards,
Nik
