Feature: Consistent localization behavior for all email templates in the Universal Login experience.
Description:
Currently, email templates behave inconsistently when handling localization and user metadata:
- Email OTP Template: The
app_metadataof the user is not accessible, and therequest_languageparameter reflects the browser’saccept_languageheader. - Reset Password Template: The
app_metadatais accessible, and therequest_languagereflects the actual language Auth0 used to render the login page. - Account Blocked Email: The
app_metadatais accessible, but therequest_languageparameter is empty.
The inconsistency in how these templates handle request_language and user metadata complicates delivering a uniform experience across different emails. A more consistent approach, where request_language reflects the rendered language in all templates and app_metadata is accessible, would streamline localization.
Proposed solution:
- Standardize
request_languageto reflect the rendered language in all templates. - Introduce a separate parameter for the
accept_languageheader. - Ensure
app_metadatais accessible in all templates.
Use-case:
We are customising and localising email OTP, password reset and account blocked emails using the new universal login experience in login page. The localisation is a bit different for all the mentioned templates.