Skip to content

SC-54452 Mention Scoped Organization Tokens in SonarQube Cloud service connection - #594

Merged
antoine-vinot-sonarsource merged 4 commits into
masterfrom
fix/ap/vss-extension-mention-scoped-org-tokens
Aug 4, 2026
Merged

SC-54452 Mention Scoped Organization Tokens in SonarQube Cloud service connection#594
antoine-vinot-sonarsource merged 4 commits into
masterfrom
fix/ap/vss-extension-mention-scoped-org-tokens

Conversation

@aurelien-poscia-sonarsource

Copy link
Copy Markdown
Contributor

Summary

  • The SonarQube Cloud service endpoint's token description and help text only mentioned personal access tokens, even though Scoped Organization Tokens generated by an organization admin are also valid credentials.
  • Updated src/extensions/sonarcloud/vss-extension.json so both the apitoken input description and the connection helpMarkDown mention this option.

Jira: https://sonarsource.atlassian.net/browse/SC-54452

Test plan

  • Validated the JSON is still well-formed.
  • Confirm the updated text renders as expected in the Azure DevOps service connection creation UI.

@aurelien-poscia-sonarsource
aurelien-poscia-sonarsource requested a review from a team as a code owner August 3, 2026 12:38
@hashicorp-vault-sonar-prod

hashicorp-vault-sonar-prod Bot commented Aug 3, 2026

Copy link
Copy Markdown

SC-54452

@antoine-vinot-sonarsource antoine-vinot-sonarsource left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@antoine-vinot-sonarsource
antoine-vinot-sonarsource force-pushed the fix/ap/vss-extension-mention-scoped-org-tokens branch from 05cdb14 to 39c70d2 Compare August 3, 2026 15:24
Both the connection description and helpMarkDown only referenced
personal access tokens, but Scoped Organization Tokens created by an
organization admin are also valid for the SonarQube Cloud service
endpoint.
@sonarqube-next

sonarqube-next Bot commented Aug 4, 2026

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed for 'Azure DevOps extension for SonarQube Server'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@sonarqube-next

sonarqube-next Bot commented Aug 4, 2026

Copy link
Copy Markdown

Quality Gate passed Quality Gate passed for 'Azure DevOps extension for SonarQube Cloud'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@antoine-vinot-sonarsource
antoine-vinot-sonarsource merged commit 58473a2 into master Aug 4, 2026
36 checks passed
@antoine-vinot-sonarsource
antoine-vinot-sonarsource deleted the fix/ap/vss-extension-mention-scoped-org-tokens branch August 4, 2026 07:16
@gitar-bot

gitar-bot Bot commented Aug 4, 2026

Copy link
Copy Markdown
Code Review ✅ Approved

Updates the SonarQube Cloud service connection documentation and input descriptions in vss-extension.json to mention Scoped Organization Tokens as valid credentials. No issues found.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants