Scoped Org Token - Service Connection internal Server error

[joew (Joe)]

when using a scoped organization token to create a new sonarcloud service connection in azure devops, we receive the following erorr messag upon verfication:

• Failed to query service connection API: ‘https://sonarcloud.io/api/organizations/search?member=true’. Status Code: ‘InternalServerError’, Response from server: ‘{“errors”:[{“msg”:“An unexpected error occurred. Please try again later.”}]}’

are scoped organization tokens not meant to be used in service connections? this should be the main use case.

• ALM used: Azure Devops
• Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
• Steps to reproduce
  • create a new azure devops service connection
  • sonarqube cloud
  • insert scoped token
  • click verify

[aurelien.poscia (Aurélien Poscia)]

Hey @joew ,

As described in the UI, as of today, Scoped Organization Tokens are only meant to be used to run an analysis:

So it works as expected.

Cheers,

Aurélien

[joew (Joe)]

And by analysis you mean exclusively manual analysis? so its pretty useless for CI-Analysis.

or how do you use that scoped token in your yaml pipeline sonarcloudPrepareAnalysis task? according to your documentation the task needs to reference the service connection

[aurelien.poscia (Aurélien Poscia)]

SOTs can of course be used for CI analysis. It is however true that they are currently not compatible with Azure Service Connections. I have flagged this to PM attention. Thanks for the feedback!