Summary
The GitLab authentication button on the login page displays a broken image fallback instead of the GitLab logo.
The browser requests the following asset:
/images/alm/gitlab.svg
This request returns 404.
However, in the SonarQube container, the GitLab logo exists only under the theme-specific directories:
/opt/sonarqube/web/images/alm/light/gitlab.svg
/opt/sonarqube/web/images/alm/dark/gitlab.svg
There is no file at:
/opt/sonarqube/web/images/alm/gitlab.svg
As a result, the browser renders the image alt text (GitLab), which overlaps with the existing button label.
Environment
- SonarQube Community Build:
26.9.0.129388 - Deployment method: official SonarQube Helm chart
- Authentication provider: GitLab
- GitLab authentication itself works correctly
- The issue only affects the provider logo displayed on the login page
Steps to reproduce
- Deploy SonarQube Community Build
26.9.0.129388using the official Helm chart. - Configure GitLab authentication.
- Open the SonarQube login page.
- Observe the GitLab authentication button.
Actual behavior
The GitLab logo is not displayed.
The frontend requests:
GET /images/alm/gitlab.svg
which returns:
404 Not Found
The container filesystem contains:
/opt/sonarqube/web/images/alm/light/gitlab.svg
/opt/sonarqube/web/images/alm/dark/gitlab.svg
but does not contain:
/opt/sonarqube/web/images/alm/gitlab.svg
Because the image cannot be loaded, the browser displays the alt text (GitLab) in its place, causing it to overlap with the authentication button text.
Expected behavior
The login page should load the GitLab logo from the appropriate theme-specific asset path, for example:
/images/alm/light/gitlab.svg
or:
/images/alm/dark/gitlab.svg
depending on the active theme.
Alternatively, if the frontend is expected to request:
/images/alm/gitlab.svg
then that asset should be included in the distribution.