GitLab incoming mail token
ID gitlab_incoming_mail_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 in the email address to which a user sends mail to create issues or merge requests in a GitLab project. GitLab gives these tokens the prefix glimt-, which cannot be configured. GitLab does not document the length; the regexp follows the gitleaks rule (25 characters after the prefix).
- 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
^glimt-[A-Za-z0-9_-]{25}$Python re syntax.
Examples
| Value | Description |
|---|---|
| glimt- 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_incoming_mail_token - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/gitlab_incoming_mail_token.yamlon GitHub