Auth0 Home Blog Docs

Client Logo in Hosted Page lock widget?

hosted-login-page
logo

#1

I have multiple clients, each should display their own logo in the Hosted Login Page.

Is there any way I can pull this in from the Client Settings? I tried console logging out the config in the hosted login script and I don’t see the Client Logo anywhere.

Thanks!
Joe


#2

I don’t believe there’s any built-in support for this in the hosted login page; there is however support for this in the consent screen (https://auth0.com/docs/api-auth/user-consent#consent-dialog). I believe the reasoning here would be that the hosted login page should present a single branding that is associated with your service and not so much individual applications within the service while the consent dialog is indeed specific to the application requesting consent (granted that if the applications in question are all first-party you may even not be showing the consent screen in the first place).


#3

Would it be possible to pass the client logo url as part of the config sent to the hosted page?

    var config = JSON.parse(decodeURIComponent(escape(window.atob('@@config@@'))));

If the client logo is available there it would be easy to configure the lock logo based on this URL.


#4

It would be technically possible, but not aligned with what I mentioned before about the notion above that the hosted login page should not be branded by client application, but by the service to which it is associated.

For example, if you service example.com you would have an Auth0 tenant like example.auth0.com and ideally you would have a custom domain identity.example.com that points to example.auth0.com so that the URL end-users see when accessing the hosted login page is in your own TLD.

With this in mind, the branding of the login page should be all about the service Example and not about a particular client application that is defined within that service. It would be normal to have different client applications to handle web and native scenarios, but the brand should still reflect the Example service.