Assets in Login v2
⚙️Configuration🏬Self-hosted❌Unsolved❓Question🪲Bugs
We have deployed a test environment having the api server and login ui v2 on different domains (goal is multiple customer facing Login V2 with a single backend in a B2B tenant setup). Reason is higher customization of the login docker container (e.g. background images).
So far so good, login works. But with the branding part available in the backend we fail with images and fonts - a bug in the code or my setup
For image assets we get invalid urls in the browser and the font asset seam to be ignored (maybe not yet covered), we get Lato.
So we discuss here just logos, icons.
While api server is serving on
the browser is showing
So most likely somewhere in the Login project the urls are replaced (which is wrong except the login v2 next app would proxy and serve these assets).
As many run in the Zitadel standard setup with single domain and traeffik, all tests are passing and most likely not many of you also faced the issue, but still hoping to be lucky here with my post to find an answer.
Does anyone of you have an idea if I can overcome with a config change?
Maybe @Rajat ?
Many thanks.
So far so good, login works. But with the branding part available in the backend we fail with images and fonts - a bug in the code or my setup
For image assets we get invalid urls in the browser and the font asset seam to be ignored (maybe not yet covered), we get Lato.
So we discuss here just logos, icons.
While api server is serving on
/v2/settings/branding/v2/settings/branding ..., "logoUrl":"https://zitadel-test.adattada.com/assets/v1/372727755239928577/policy/label/logo-373615965985885506", ... ..., "logoUrl":"https://zitadel-test.adattada.com/assets/v1/372727755239928577/policy/label/logo-373615965985885506", ...the browser is showing
404 - https://zitadel-ui-test.adattada.com/assets/v1/372727755239928577/policy/label/logo-373615965985885506404 - https://zitadel-ui-test.adattada.com/assets/v1/372727755239928577/policy/label/logo-373615965985885506So most likely somewhere in the Login project the urls are replaced (which is wrong except the login v2 next app would proxy and serve these assets).
As many run in the Zitadel standard setup with single domain and traeffik, all tests are passing and most likely not many of you also faced the issue, but still hoping to be lucky here with my post to find an answer.
Does anyone of you have an idea if I can overcome with a config change?
Maybe @Rajat ?
Many thanks.
