GitLab runner authentication token
ID gitlab_runner_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 with which a GitLab Runner authenticates to a GitLab instance to pick up CI/CD jobs. GitLab gives these tokens the prefix glrt- (glrtr- for runners created with a registration token), which cannot be configured. GitLab does not document the length; the regexp follows the gitleaks rule (20 characters after the prefix, or the longer routable form t<digit>_... ending with a dot and a nine-character suffix).
- 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
- 70/100 · missing: examples, mapping (Wikidata, Schema.org, ...), translation
- Metacrafter rules
- no detection rule yet
- Supported by tools
- Datadog Sensitive Data Scanner, GitGuardian, GitHub secret scanning, Gitleaks
Regular expression
^glrtr?-(?:[A-Za-z0-9_-]{20}|t[0-9]_[A-Za-z0-9_-]{27,300}\.[0-9a-z]{9})$
Python re syntax.
Examples
| Value | Description |
|---|---|
| glrt- invalid | Prefix without the token |
Sources
- doc: https://docs.gitlab.com/security/tokens/
- other: https://github.com/gitleaks/gitleaks/blob/master/config/gitleaks.toml
Use this record
- Page URL:
https://registry.apicrafter.io/datatype/gitlab_runner_token - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/gitlab_runner_token.yamlon GitHub