Gitlab authentication is not showing the button to connect

SonarQube Server / Community Build
1

Sonarqube community edition v10.7
Deployed with helmchart and a postgresql database running on a pod in a kubernetes cluster

I’m trying to set up GitLab authentication. I followed the tutorial by enabling just-in-time authentication in the GitLab section and providing an application token from our GitLab. The configuration seems fine, but no GitLab login button is displayed. There’s nothing in the logs. Any ideas are welcome.

2

Hi,

Welcome to the community!

SonarQube 10.7 is already EOL. Can you bump your version up to 25.3 and try again?

 
Thx,
Ann

3

Hello!

I can’t find version 25.3, but I upgraded to 25.2 and I’m still experiencing the same issue. The configuration looks correct, but the GitLab authentication button isn’t showing up. This isn’t our production environment — we’re using it to test the upgrade. I’m concerned the same problem will occur in production if we proceed with the upgrade. Where can I check to see what’s going wrong?

Thanks in advance,

4

Hi,

25.4 is the current version now.

Once you get there, can you provide a screenshot?

 
Thx,
Ann

5

Hello,

I’m up to date on the current version, I join the screenshots of my gitlab auth configuration. Thanks for your reply.

Screenshot from 2025-04-28 09-55-36
Screenshot from 2025-04-28 09-55-361342×814 70.9 KB

Screenshot from 2025-04-28 09-55-58
Screenshot from 2025-04-28 09-55-58618×813 55.2 KB

6

Hi,

Thanks for the screenshots.

To confirm, the missing button is the “Log in with GitLab” button on the login page, right?

What, if anything shows up about this in your web.log?

 
Thx,
Ann

7

Yes the button “log in with gitlab” is not on the login page and no errors in the logs web.log

8

Hi,

Thanks for the confirmation. I’m not sure where to go from here, so I’m going to flag this for more expert eyes.

 
Ann

10

It seems nothing I do (bad config, etc.) stops the button from showing up!

I would be curious to know what the results are of API calls like below against the SonarQube instance where you’re having trouble. Here is what I have:

http://localhost:9000/api/v2/dop-translation/gitlab-configurations

{
  "gitlabConfigurations": [
    {
      "id": "gitlab-configuration",
      "enabled": true,
      "applicationId": "1234",
      "url": "gitlab.com/",
      "synchronizeGroups": true,
      "allowedGroups": [],
      "allowUsersToSignUp": false,
      "provisioningType": "JIT",
      "isProvisioningTokenSet": false,
    }
  ],
  "page": {
    "pageIndex": 1,
    "pageSize": 1000,
    "total": 1
  }
}

http://localhost:9000/api/users/identity_providers

{
  "identityProviders": [
    {
      "key": "gitlab",
      "name": "GitLab",
      "iconPath": "/images/alm/gitlab.svg",
      "backgroundColor": "#6a4fbb"
    }
  ]
}
11

Hello! I tried both commands, the first one returns this:

{
  "gitlabConfigurations": [
    {
      "id": "gitlab-configuration",
      "enabled": true,
      "applicationId": "26af657acd7ec75f8e7f351ee9696e92a2a7f63a57774edf52baf18d14c53ae3",
      "url": "https://gitlab.ehp.red",
      "synchronizeGroups": true,
      "allowedGroups": [],
      "allowUsersToSignUp": true,
      "provisioningType": "JIT",
      "isProvisioningTokenSet": false,
      "errorMessage": null
    }
  ],
  "page": {
    "pageIndex": 1,
    "pageSize": 1000,
    "total": 1
  }
}

and the second one return this:

{
  "identityProviders": []
}
14

Hi @mmoutama :vulcan_salute:

I was unfortunately not able to reproduce.

Could you try to set it up from a scratch with a fresh SonarQube Server Instance?