SonarCloud tokens are tied to the user that added the project

[mikefede]

Hi Colin,
Looks like several similar requests have been submitted before:

Shared API key for CI tools?

We’re using Github login for our account, however we want to link Sonarcloud with our CI tools. Per best practice, we don’t want to use a user’s keys, rather a simple shared read only account. I haven’t worked out how to do this other than the very cumbersome approach of creating a dedicated Github CI user, which is further complicated as we mandate MFA on our Github accounts. Does anyone know how best to mange CI API integration and whether dedicated accounts are needed for this?

Security token that is not tied to the user but to organisation

Hi, I am analysing repos from an open source project using SonarCloud. All repos have analysis done via Github actions. For this, the token used is user token (my account->security). Question is simple: what happens to these integrations if I leave the org. Or I close my account from SonarCloud as the tokens are attached to user and not organisation. Will it make any difference if I have another person as admin on the organisation?

Is there a way to use app registeration instead of using Personal Access Token in AzureDevops?

We would like to give access to SonarCloud with another mechanism than using PAT. Since PAT is tied to a user account, if that account gets closed on AzureDevops we need to change the token again. Is there another way of integrating SonarCloud in AzureDevops?

machine/CI user token

Hi, Is there a way to generate a token that can be used by the CI that’s not tied to a specific account? Our use case is that we are using the SonarQube Scanner plugin for Jenkins and connecting it to SonarCloud. This works fine as long as we use the same token for each project, but currently that token is attached to a single user account, which means that user has to create each project individually. This is becoming time-consuming, and we would like other users to be able to create their own…

There was also a feature added to the development roadmap a few years back but never implemented: SonarCloud Community - Issues - Jira

Any chance this will be prioritized on your roadmap in the near future?