SonarQube token
ID sonarqube_token
DatatypeNot PIIidentifierDraft
This record is a draft: it has not been reviewed yet and may be incomplete or wrong. Do not rely on it for compliance decisions. Help improve it (see CONTRIBUTING.md).
Token of SonarQube Server used to run an analysis or call the web API instead of a login and password. Current tokens start with one of the prefixes squ_, sqa_ and sqp_, which depend on the token type (user, global analysis or project analysis token), followed by 40 characters. Older tokens without a prefix are not covered by the regexp.
- Parent datatype
- Access token
access_token - Categories
- Secrets and credentials (passwords, keys, tokens)
- Countries
- Global (not tied to a country)
- Languages
- Common to most languages
- Quality
- 78/100 · missing: second example, mapping (Wikidata, Schema.org, ...), translation
- Metacrafter rules
- no detection rule yet
- Supported by tools
- Gitleaks, Semgrep, TruffleHog
Regular expression
^sq[uap]_[A-Za-z0-9=_-]{40}$Python re syntax.
Examples
| Value | Description |
|---|---|
| squ_example0example0example0example0example0 | Constructed, non-functional value |
| example0example0example0example0example0 invalid | No type prefix |
Sources
- doc: https://docs.sonarsource.com/sonarqube-server/latest/user-guide/managing-tokens/
- doc: https://docs.aws.amazon.com/secretsmanager/latest/userguide/mes-partner-SonarQubeToken.html
- other: https://github.com/gitleaks/gitleaks/blob/master/config/gitleaks.toml
Use this record
- Page URL:
http://registry.apicrafter.io/datatype/sonarqube_token - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/sonarqube_token.yamlon GitHub