Feature: Per-application branding / per-organization branding with custom login/mfa challenge pages.
Description: I would like support for branding at the auth0 organization or application level, but I have a classic custom login and mfa page.
Use-case: I am trying to build an application where I need to brand the various auth0 (login, mfa, reset password, etc) pages for different clients. The options, as far as I can tell, are
- Use per-organization branding. → Might work, but the project I’m working on has a legacy custom login page, which seems to be incompatible. (Might also require users who login with an organization parameter to be a member of that organization, this is backfillable though)
- Create a different tenant for each brand → Lots of work to make sure the tenants match up exactly except for branding, and will require changes to downstream consumers of our tenants.
- Use ACUL → requires a custom domain, which isn’t a lot of work, but the ACUL setup seems very complex for what I want, just replacing the colors/icons on the pages.
Per-organization branding would be great, but having a custom login page precludes it from working. I noticed there is are Management API endpoints to get/create brandings, but it only supports one branding per-tenant, maybe this could be extended to support multiple brandings, which could be automatically applied if you sent a brand_id parameter in auth0 requests?
Basically I’m stuck between a rock and a hard place here, forced to implement very complex solutions for things that should honestly not be very hard.