Primary color (dark mode) is no valid Hex color value (POLICY-391dG)
I come with a very weird bug 🤣 🐛
As you might know, we configure Zitadel mostly as code.
So did we the First and Default Instance. Only did I make one tiny mistake:
Before
After
Now, so far so good, the change is also rolled out (see Argo screenshot [white bg]). The deployment was also properly restarted by the change detection and twice by me but still the change does not get reflected, the UI stays unreadably wrong and if you click Branding this error shows.
Also, sadly, saving from the UI the new color does not have any effect.
Do you happen to know where I lack a piece to fix? Is that color stored wrongly into the DB at all?
Due to #enterpriseDebt we are on v2.70.13 still but migrations have started 🚛
TQ all 🌈
6 Replies
Hey there @Dom thanks for sharing the details on this on this front. I will escalate it to some of our team and see what they think. @fcoppede can you take a peak sir? Thanks!
👋 hello @Dom! Thanks for reaching out to us, I've forwarded this question to our Engineering team, as soon as I get a response I'll get back to you, thanks for your patience!
Any update @fcoppede. As you can see it doesn't look to great still 🤣
hello @Dom apologies for the delay in getting back to you, to fix this, you need correct the colors on the already existing instances and/or organizations. I'm following up with Engineering to get additional details on how to do this. Thanks!
I kind of inferred that already and tried (see original screenshots). Somehow it does not take effect. So maybe you must tell the engineers that saving it on the instance doesn't work 😦 If I come back to the page its reset.
hello @Dom, there are 2 things to fix, one that this values can't end up in the setup, and second that you can still correct them.
For the mainly, if you do an API call with the correct values for the instance, it should resolve the problem:
Do https://zitadel.com/docs/apis/resources/admin/admin-service-get-preview-label-policy to get all values,
Then https://zitadel.com/docs/apis/resources/admin/admin-service-update-label-policy to correct the value
Then https://zitadel.com/docs/apis/resources/admin/admin-service-activate-label-policy to activate it
Let me know how that goes, thank you!
ZITADEL Docs
Returns the preview private labeling/branding configured on the instance level. The preview is used to show you how it will look like, and not activate it directly for your users. In the future, it should be possible to send a preview mail and have a look at the preview login. The settings will trigger if the organization has not overwritten the...
ZITADEL Docs
Update the preview private labeling/branding configured on the instance level. It affects all organizations, that don't overwrite the settings. The preview is used to show you how it will look like, make sure to activate it as soon as you are happy with the configuration. Define what colors, fonts, and logo should be used for the Login/Register ...
ZITADEL Docs
Activates the preview private labeling/branding configured on the instance level. It will be shown to the users afterward. It affects all organizations, that don't overwrite the settings. Defines what colors, fonts, and logo should be used for the Login/Register UI, E-Mails and Console.