# Changed Gitlab group sync API call

**URL:** <https://community.sonarsource.com/t/changed-gitlab-group-sync-api-call/89983>\
**Category:** SonarQube Server / Community Build\
**Tags:** gitlab\
**Created:** [April 27, 2023, 11:35am UTC](https://community.sonarsource.com/t/changed-gitlab-group-sync-api-call/89983 "2023-04-27T11:35:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hermanns](https://avatars.discourse-cdn.com/v4/letter/h/ecb155/32.png) [@Hermanns](https://community.sonarsource.com/u/Hermanns)\
**Post date:** [April 27, 2023, 11:35am UTC](https://community.sonarsource.com/t/changed-gitlab-group-sync-api-call/89983/1 "2023-04-27T11:35:54Z")

</div>

Hi,

- which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  - sonarqube 9.9 community

- how is SonarQube deployed:
  - Helm, K8s

- what are you trying to achieve
  - return to behavior of 8.9-LTS group synchronization

- what have you tried so far to achieve this
  - analyzed change, found the [causing issue](https://sonarsource.atlassian.net/browse/SONAR-15171) and [open ticket for possible solution](https://sonarsource.atlassian.net/browse/SONAR-15674).

can some one help on this issue we got after upgrade from 8.9-LTS to 9.9-LTS.

With this issue ([[SONAR-15171] - Jira](https://sonarsource.atlassian.net/browse/SONAR-15171)) the list of returned groups  
for synchronization was reduced by adding `min_access_level=10` to the Gitlab API call.

```auto
(server/sonar-auth-gitlab/src/main/java/org/sonar/auth/gitlab/GitLabRestClient.java)

8.9: API_SUFFIX + "/groups", scribe, accessToken, GsonGroup::parse);
->
9.9: API_SUFFIX + "/groups?min_access_level=10", scribe, accessToken, GsonGroup::parse);

```

This is now filtering out groups visible because of child sharing.

After migration from 8.9-LTS we are now facing an great issue with this change in our Gitlab permission setup and would like to switch back to the old behavior.

There was already a discussion ([add option to enable group sync at parent level by Guimove · Pull Request #3281 · SonarSource/sonarqube · GitHub](https://github.com/SonarSource/sonarqube/pull/3281)) with some proposed code changes to add an option switch  
which led to this still open Sonarsource ticket ([[SONAR-15674] - Jira](https://sonarsource.atlassian.net/browse/SONAR-15674)).

Is there any chance that this will be realized?  
Is there another way to return to the old behavior?

Thanks for any help in advance  
Cheers

---

<div class="post-metadata">

**Author:** ![Mathieu\_Suen](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mathieu_suen/32/9079_2.png) [@Mathieu\_Suen](https://community.sonarsource.com/u/Mathieu_Suen)\
**Post date:** [June 1, 2023, 9:27am UTC](https://community.sonarsource.com/t/changed-gitlab-group-sync-api-call/89983/6 "2023-06-01T09:27:19Z")

</div>

Hi @Hermanns

Thanks for your feedback. The fix is not trivial, and we need to investigate possible solutions. We do not have any timeline yet and will update the [SONAR-15674](https://sonarsource.atlassian.net/browse/SONAR-15674) once fixed.

Thanks for your comprehension