Issue starts appearing on Azure pipeline during SonarCloudPrepare step.
we get error:
Failed to request and parse ‘https://sonarcloud.io/api/qualityprofiles/search?project=obfuscated&organization=obfuscated’: Response status code does not indicate success: 403 ().
Hey there.
This would indicate that the token provided to your SonarCloud Service Connection (that you’ve then elected to use in your Azure DevOps pipeline configuration) doesn’t have the correct permissions.
I would recommend using a new token generated from SonarCloud, generated by a user you’re sure has access to the project in question.
but the issue still exists.
While this indicates a successful connection to SonarCloud, it doesn’t mean that token has rights on the project. Did you generate a new token that is being used here, from a user you know has access to the project you’re trying to analyze?
Hmm… I have the same issue. But am struggling to break through.
When pulling the mentioned URL just in the browser. I get a code 200, and about 600 lines of json code.
I’m having the same issue here. Full permission to my user on organization and project. Fresh token, and still having de 403 response.
One thing that I noticed, I’m using the SonarScanner with the following command:
SonarScanner.MSBuild.exe begin /o:“my-organization” /k:“my-project-key” /d:sonar.host.url=“https://sonarcloud.io” /d:sonar.token=“my-token”
On my profile, in security section, I can see the token that was generated, and it shows the token was never used.
I generated another token, and tried again, and still have de 403 response and the new token also shows it was never used.
So, I did use the first one token to connect SonarLint on Visual Studio and it was done with no errors, and after that, the token shows it was used less than one hour ago.
What is possibly wrong with the command I’m using that the token seems not being using on the request?
This post helped me solve the problem.
When using SonarCloud the parameter to informe the token must be sonar.login and not sonar.token as I was using.
Well, after all, I just discovered I was using an old version of sonar scanner that does not support sonar.token parameter. I updated to the latest version and it says now supports sonar.token parameter as well as token.login