Sorry for my late reply, we just tried it again to make sure we can report the issue as accurately as possible.
Status Quo
What we did
- Visited SonarQube Cloud
There we saw the following
“Status of your current token” does not bother us, as everything seems to work fine.
Updating the token with “Reporter” permissions
Now we tried to update this token with a new one
For this we:
- Created a new token with API permission on our existing “technical user” (Access Level “Reporter”)
- Tried to update the token in Sonar Cloud
Result:
“You need to have admin access on the group”
is expected
But like detailed in the before mentioned issue, “Owner”(=Admin) permissions should not be required for what SonarCloud is trying to do in GitLab
GitLab user for organisation and GitLab users permissions, does it really have to be Owner and why?
Updating to “Owner” permission and reusing token
Next we changed to User to have Admin rights (GitLab calls that “Owner”).
For this we:
- Switched the rights of the “technical user” to “Owner”(=Admin)
- Tried to apply the same token as before in Sonar Cloud
Result:
“You need to have admin access on the group”
This is not expected and the new token should be accepted
Updating the token with “Owner” permissions
Not sure if this might be a caching issue, we generated a new token, with the “technical user” having “Owner” (=Admin) rights throughout.
For this we:
- Revoked token which was used for previous attempt
- Created a new token with API permission on our existing “technical user” (Access Level “Owner”)
- Tried to update the token in Sonar Cloud
Result:
“You need to have admin access on the group”
This is not expected and the new token should be accepted
Conclusion
At the Moment Sonar is working for us with GitLab.
We cannot update our GitLab token.
If our token would have an expiry date, SonarCloud integration would break for us.
We tried this on 22-09-2022 between 12:00 and 12:10 UTC if that helps with debugging.