smileBeda
(Beda Schmid)
April 24, 2025, 2:14am
1
I found these two tickets saying the setting is broken which appeared to be due to cross origin policy.
Hi,
After upgrade from SonarQube 10.4.1 to 10.5.0 the logo we are using on the property ‘sonar.lf.logoUrl’ doesn’t work anymore.
I tried with different image, but it’s always the same.
Looks there was some changes on cross origin. I didn’t saw anything on the release notes
[sonarqube_logo]
[cross_origin]
An external logo was working on 9.9 LTS and 10.4.1
Thanks
In my case, custom logo just does not apply at all.
This is what I see, no matter if I add svg, png, jpeg, avif, webp, with or without set width, after or not clearing browser caches.
I can see it in the backend. But … the logo is the logo, right?
Am I “confusing” something?
ganncamp
(G Ann Campbell)
April 25, 2025, 1:01pm
2
Hi,
What logo do you see at the top-left after you log in?
Ann
smileBeda
(Beda Schmid)
April 25, 2025, 2:24pm
3
The correct one indeed (the one I set)
I can see it in the backend. But … the logo is the logo, right?
This is what I mean:
the screenshot I shared is from the log in, where the default logo shows.
So this is not customizable?
Thanks
ganncamp
(G Ann Campbell)
April 25, 2025, 2:26pm
4
Hi,
To be honest, I’m not sure. I suspect this was overlooked when the login was reworked. So I’m going to flag this for the experts.
Ann
1 Like
Hello @smileBeda ,
I see that this is as per design. It’s only after the login you see the custom logo which you see as well. I will flag this to our product manager and see if we can have a quick win here. I will keep you posted.
Thanks,
Sarath