We are a Sonar Qube Cloud customer.
We are facing an issue while analyzing a new project in SonarQube Cloud. Earlier, we were able to analyze new projects without any problems, but now, when we go to the Analyze new project page we are getting this error: “The Azure DevOps access token is not valid. Reasons: The token doesn’t have the required permissions (Code: Read & Write).” We have already checked the Personal Access Token, and it is still active and it have Read & Write permission.
Could you please help us solve this?
Does the token have access to all repos? Is it possible that it currently only had access to a few, and the repo in question isn’t one of them?
Does the user who the token got generated under also still have access to the repos? I assume the user is still active as well?
Possible to create another new token and test with that?
Yes the token have access to all repo….. also till last month we were able to analyze new projects with this same token.
The main issue is the newly created projects was not even showing in the repo’s Project page of SonarQube cloud. And also while we are trying to open the Analyze new project page it was blank and giving this error “The Azure DevOps access token is not valid. Reasons: The token doesn’t have the required permissions (Code: Read & Write).”
It’s hard to say without looking into the environment. Can you double-check that the specific token has the mentioned Code: Read & Write permissions and that it’s not expired yet. Could you test the token against the Azure API directly to see if it works. Lastly, is it possible to test with another newly created token?