- Enterprise Edition
- Version 8.6.1 (build 40680) - I know we are behind but beyond my control
- Users are from SSO and SAML integration
- Add a new project through Gitlab - hosted on gitlab.com.
- User is not an owner but developer on the project, the documentation states read_access scope is enough
- We have tried: creating new tokens with broader scope, waiting 12+ hours still facing same error
Hey there.
Newer versions (including SonarQube v8.9 LTS) should provide a more descriptive error message around why the token couldn’t be validated. SonarQube v8.6.1 is not just “behind”, but an EOL version of SonarQube, and has been for well over a year now.
Feel free to come back if the issue persists after landing on the LTS.