GitLab OAuth application secret
ID gitlab_oauth_app_secret
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).
Client secret of an OAuth application registered in GitLab. GitLab gives these tokens the prefix gloas-, which cannot be configured. GitLab does not document the length; the regexp follows the gitleaks rule (64 characters after the prefix).
- Parent datatype
- API key or client secret
api_key - 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, GitHub secret scanning, Gitleaks
Regular expression
^gloas-[A-Za-z0-9_-]{64}$Python re syntax.
Examples
| Value | Description |
|---|---|
| gloas- invalid | Prefix without the secret |
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_oauth_app_secret - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/gitlab_oauth_app_secret.yamlon GitHub