Nine more GitLab token types are now redacted, and the older patterns catch modern longer tokens.
What's wrong with this entry?
Secret redaction now recognises nine more GitLab credential types, and the two existing rules were rewritten to accept longer tokens. Previously only exactly-20-character glpat- and deploy tokens matched; the shared pattern now accepts 20 or more characters plus an optional 9-character checksum suffix, so current GitLab tokens are caught.
- New detectors: runner authentication (
glrt-), OAuth app secret (gloas-), pipeline trigger (glptt-), Kubernetes agent (glagent-), incoming mail (glimt-), SCIM OAuth (glsoat-), CI build (glcbt-), feed (glft-) and feature flag client (glffct-) tokens. - All eleven are marked high confidence, and the list is built unconditionally at startup, so this is live for everyone on this build.
- The name prettifier learned
ci: "CI"andscim: "SCIM"so rule names render correctly.
gitlab-scim-oauth-token, [\\w=-]{20,}(?:\\.[0-9a-z]{9})?
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Secret redaction covers more Slack tokens and any length of private key
Both mention secret redaction
-
v2.1.234
Secret scanner detects Anthropic OAuth tokens
Both mention secret redaction
-
v2.1.234
Slack workflow tokens and webhook URLs are scrubbed
Both mention secret redaction