As the title says the new Gitlab Auth requires the api scope unlike the community plugin which only needed read_users and worked fine proving there is no need for the api scope to use Gitlab as an authentication provider. Whats the need for api scope in SonarQube 8.0? Are there additional calls Son…

New Gitlab Auth uses `api` scope instead of `read_users` scope

pierreguillot (Pierre Guillot) December 18, 2019, 9:03am 9

Topic		Replies	Views
GitLab ALM Integration error SonarQube Server / Community Build	4	2630	July 13, 2020
SonarQube 10.4 - GitLab authentication scope change SonarQube Server / Community Build	10	1328	March 4, 2024
Scope permissions for GitLab group sync SonarQube Server / Community Build sonarqube , gitlab , authentication , api , sync	5	57	February 27, 2025
SonarCloud API access token rights with Gitlab SonarQube Cloud gitlab , tokens , secrets	7	2773	April 28, 2022
Gitlab authentication with release 10.5.0.89998 SonarQube Server / Community Build	14	1290	May 10, 2024