redact-secret · Report

Management API token (SSWS)

00-prefixed 42-character API token sent as Authorization: SSWS; recognized beside the SSWS scheme or a same-line okta keyword.

Okta
Detectors: okta-api-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

All providers

Dossier verdictReady
Dossier evidence levelT2 · Tool-corroborated
Dossier researched2026-09-29

redact-secret#315 (product PR #681) landed on the product main after 0.1.0-beta.6; the pinned published package predates it. OAuth access/ID tokens are JWTs and belong to the jwt family, not this one.

New pipelineAuthority

Built from the new pipeline

The new pipeline is the authority for credential qualification. These numbers are read from the qualification view derived from the official credential-eval run of the public-evidence-snapshot population. The regression and policy populations keep their own counts on the qualification pages and are not added in here.

Authority: new
Population: public-evidence-snapshot
Engine: credential-eval 0.1.0-alpha.16
Evidence: snapshot-2026.10.06.4
Run: sha256:4bec6e539482…
Recorded: 2026-10-07
Authorised for: @redact-secret/core@0.1.0-beta.14

Maintainer-reviewed (independent review pending)

598 fixtures of the 7,041 in evidence release snapshot-2026.10.06.4 carry this label. They are counted in the numbers on this page.

Passed the project’s own verification (source evidence, automated checks, recorded counter-arguments); not yet independently reviewed.

OpenRedaction default (all patterns): not measured in this run (optional)

The default (all-pattern) profile is slow and noisy for credential evaluation: personal data and resource identifiers dominate its findings, and its last official measurement took 7 minutes of scanner time on a population the credential profile scans in seconds (its methods run takes 40+ minutes), so it is a manual measurement and never blocks other scanners or core verification (#763). Its earlier results stay as history with their run identity; the credential profile is a separate scanner, never spliced with it.

Last measurement: policy-corpus@linux-x64 (configuration sha256:2451ce7bf380), public-evidence-snapshot+methods@linux-x64 (configuration sha256:d47d081ce5fb), public-evidence-snapshot@linux-x64 (configuration sha256:2451ce7bf380), regression-corpus@linux-x64 (configuration sha256:2451ce7bf380) · engine 0.1.0-alpha.5 · recorded 2026-10-05 · retained record, no longer listed by the run registry. It stays labelled with that run identity and is never combined with another profile or another run.

Open the qualification page for this pointer

OpenRedaction credential profile (33 types): not measured in an official run (local exploratory diagnostics only: see ADR)

The credential profile is the comparison profile chosen in docs/decisions/2026-10-06-choose-the-openredaction-credential-bearing-profile-as-the-comparison-scanner.md. It is optional in the official run class because no pinned engine configuration measures it yet: making it required would refuse every official view until the owner approves the one profile-only run. Its own history starts with that run; nothing of the default's is reused for it.

No earlier measurement of it is recorded. Nothing is shown in its place.

Official measurement: pending: requires owner approval (one profile-only run; see the decision).

Open the qualification page for this pointer

Every population and its qualification

Research record

From credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0. It describes the research on the format, not what any scanner or the product does, and not a support status.

Review stateDraft, not reviewed
Format revision1 · current
ResearchResearched
Researched2026-09-29

3 events in the review history: 2 observed, 1 reviewed. Latest: observed on 2026-09-29 by automation, project maintainer. Project-maintained review is not independent validation. The family record at this release.

Format

Provider format research from credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0.

What it looks like

Descriptive pattern: ^00[A-Za-z0-9_-]{40}$

Parts are shown as recorded. Evidence classes belong to the facts below; no class is assigned to a part.

Format facts

Provider documented · mutable-property-source · current · observed 2026-09-23
Documentation for the one property varied in legacy twin fixtures (SSWS authorization example): the guide states "Authorization: SSWS 00QCjAl4MlV-WPXM...0HmjFx-vbGua", establishing the SSWS scheme and a value that begins with the literal 00. It backs a prefix twin only; the 40-byte body length and its alphabet stay tool-corroborated and the positive tier is unchanged
- developer.okta.com/docs/guides/create-an-api-token/main/provider-documentation · last read 2026-09-29 · latest outcome read · supports the guide states "Authorization: SSWS 00QCjAl4MlV-WPXM...0HmjFx-vbGua", establishing the SSWS scheme and a value that begins with the literal 00. It backs a prefix twin only; the 40-byte body length and its alphabet stay tool-corroborated and the positive tier is unchanged
Tool corroborated · tool-corroboration · current · observed 2026-09-23
Pinned scanner rules are consistent with the contract grammar (2 artifacts: gitleaks 8.30.1; trufflehog 3.97.4).
- gitleaks/gitleaks @ v8.30.1: config/gitleaks.tomlscanner-rule-source · last read 2026-10-04 · latest outcome read · supports gitleaks 8.30.1: gitleaks.toml
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/okta/okta.goscanner-rule-source · last read 2026-09-23 · latest outcome read · supports trufflehog 3.97.4: okta/okta
Tool corroborated · dossier-research · current · observed 2026-09-29
Legacy dossier research (verdict ready, tier T2) cited 5 sources; the dossier does not attribute sources to individual properties.
- developer.okta.com/docs/guides/create-an-api-token/main/provider-documentation · last read 2026-09-29 · latest outcome read · supports Cited by the legacy dossier research for this family
- okta/okta-developer-docs @ 8aff3329cb8e651d2182ce6dcd5ebd303b42a690: packages/@okta/vuepress-site/books/api-security/api-keys/other-options/index.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Cited by the legacy dossier research for this family · #L18
- okta/okta-developer-docs @ ae696b9f70cd1bca21f640f4ad3bbdff461279ff: packages/%40okta/vuepress-site/docs/guides/oie-upgrade-api-sdk-to-oie-sdk/main/index.mdprovider-documentation · last read 2026-09-29 · latest outcome read · supports Cited by the legacy dossier research for this family
- okta/okta-management-openapi-spec @ 74fcd17fad54332caee96ebbb11fd7f203b03e4f: dist/current/management-dev-noEnums-minimal.yamlprovider-documentation · last read 2026-09-29 · latest outcome read · supports Cited by the legacy dossier research for this family · #L60548
- redact-secret/redact-secret @ add1188fed9993723c59fbce8c867086b9d2049a: docs/audits/evidence/1013/okta-api-token.mdproject-research-note · last read 2026-09-29 · latest outcome read · supports Final research evidence recorded by the legacy dossier
Unresolved · taxonomy-sources · current · observed 2026-09-29
The legacy taxonomy lists 1 source for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- developer.okta.com/docs/guides/create-an-api-token/main/provider-documentation · last read 2026-09-29 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy

Open questions

No open question is recorded for this revision.

Benchmark dossier notes

From the provider dossier, as written. The evidence level above says how well the format is backed; a fact the dossier does not record is not shown.

Shape: literal 00 then 40 characters, 42 in total. Alphabet: TruffleHog and Nosey Parker use [A-Za-z0-9_-]; gitleaks and betterleaks also allow =. Of 52 distinct non-placeholder public candidates, 47 were 42 characters, none contained =, and _ and - were both common. Okta's own migration guide shows an unelided value of 00 + 40 [A-Za-z0-9] (recorded in the benchmarks empirical observations, not in a core thread; the core threads show only the elided example).
Basis: T2. Provider prose shows the SSWS scheme and the leading 00 only (no length, no alphabet), but Okta's own repositories hold three dated, distinct full-length examples, all 00 + 40 alphanumeric: the OIE-upgrade guide, the management OpenAPI spec (2025-01 to 2026-03) and an API-security book page (2019) (redact-secret#1013). A 2019 devforum answer says "always 42 characters" and gives ^00[a-zA-Z0-9\-\_]{40}$; its author's staff status is not confirmed on the forum. Both 2023 items the benchmark ledger records come from one devforum thread (2023-09-21): an Okta team reply, "You should not assume a set structure for Okta's API tokens" (the same reply says there are no plans to change it), and a customer's [A-Za-z0-9-] reading whose own regex admits _. gitleaks' = comes from its generic AlphaNumericExtended helper (PR #1599), not from Okta evidence; no Okta example contains =. GitGuardian records the detector as Prefixed: False, which classifies its detector rather than the tokens. Okta does not appear in GitHub's secret-scanning partner list.
Issuance: UI only (the Okta API cannot create SSWS tokens); a free developer org works. The #694 hands-on checklist (total length, leading 00, alphabet classes, header, checksum) has no recorded result.
Contract in core: detector-families.md; detector added by redact-secret#315. No frozen evidence folder exists for #694.

In this benchmark

Fixture rows on the current run. Counts are for redact-secret in published · redact-secret 0.1.0-beta.14 mode.

Fixtures: 40
Left readable: 0
Redacted too much: 0
False alarms: 0

40 fixtures: 16 expect a redaction, 24 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T2Tool-corroborated	32	0	0	0
T3Project policy	8	0	0	0

Every scanner on the same fixtures

In run order. Counts are what each scanner recorded on this family's fixtures, whichever rules it has; a scanner with no rule for the family has nothing to report on it.

Counts per scanner on this family's fixtures
Scanner	Fixtures	Left readable	False alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engineNo rule maps to it	40	16	0
gitleaksRepository scanner · 8.30.1 · Directory scan · default rules1 rule targets it	40	6	3
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	40	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	40	12	0

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.

Open caveat: Okta states no grammar in prose and its 2023 staff answer says not to assume a structure; three provider examples agree on 00 + 40. READY-T2 once Q-OK accepts the four bounded dispositions; no issuance is required (an optional check could only close the _ question).

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.

Collisions: 00 is not a distinctive prefix; a value is claimed beside the SSWS scheme or a same-line okta keyword. TruffleHog gates on an Okta tenant domain.

Scanner rules for this family

Mapped by hand (reviewed 2026-09-30) from each scanner's pinned rule file, never from what a scanner found on the fixtures.

Peer scanner rules that target this family
Scanner	Rule	What the rule matches
gitleaks · rules 8.30.1	`okta-access-token`	okta keyword + 00 + 40 characters
trufflehog · rules 3.97.4	`okta`	.okta domain + 00 + 40 characters

No rule maps to this family in flare-redact, openredaction.

Find

Evidence level

Scanners

40 of 40 rows

Fixtures in this family

40 rows, redact-secret's outcome on each. Rows that need a look come first (0), then the rest in corpus order. Choose "Every scanner" to see each scanner's outcome for the same rows.

Fixtures in Management API token (SSWS)
Fixture	Kind and evidence	redact-secret
`okta-api-token-actions-env`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-compose-env`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-curl-ssws`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-env`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-keyword-context-bare`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-keyword-context-bare-twin`okta · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-keyword-context-quoted`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-keyword-context-quoted-twin`okta · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-keyword-context-unicode-crlf`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-keyword-context-unicode-crlf-twin`okta · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-node-client`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-raw-request`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-request-log`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-settings-json`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-shell-export`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-ssws-header-bare`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-ssws-header-quoted`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-ssws-header-unicode-crlf`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-tfvars`okta · documented-format-literal	Must redactT2 · Tool-corroborated	Redacted
`okta-api-token-actions-secret-reference`okta · templated-reference	Must not flagT3 · Project policy	Quiet
`okta-api-token-api-token-listing-public-id`okta · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`okta-api-token-cli-checksum-encoded-value`okta · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`okta-api-token-docs-template-placeholder`okta · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`okta-api-token-label-prose`okta · benign-lookalike	Must not flagT3 · Project policy	Quiet
`okta-api-token-mask`okta · benign-lookalike	Must not flagT3 · Project policy	Quiet
`okta-api-token-masked-console-placeholder`okta · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`okta-api-token-postman-variable-reference`okta · templated-reference	Must not flagT3 · Project policy	Quiet
`okta-api-token-prefix-only`okta · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`okta-api-token-public-id`okta · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`okta-api-token-reference`okta · benign-lookalike	Must not flagT3 · Project policy	Quiet
`okta-api-token-rotation-note-prose`okta · prose-mention	Must not flagT3 · Project policy	Quiet
`okta-api-token-short-body`okta · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`okta-api-token-short-token-near-miss`okta · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`okta-api-token-ssws-header-bare-twin`okta · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-ssws-header-prefix-bare-twin`okta · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-ssws-header-prefix-quoted-twin`okta · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-ssws-header-prefix-unicode-crlf-twin`okta · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-ssws-header-quoted-twin`okta · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-ssws-header-unicode-crlf-twin`okta · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`okta-api-token-user-and-group-ids-public-id`okta · public-identifier	Must not flagT2 · Tool-corroborated	Quiet

Sources

Researched 2026-09-29.

Documentation and code

developer.okta.com/docs/guides/create-an-api-token/main/
github.com/okta/okta-developer-docs/blob/ae696b9f70cd1bca21f640f4ad3bbdff461279ff/packages/%40okta/vuepress-site/docs/guides/oie-upgrade-api-sdk-to-oie-sdk/main/index.md
github.com/okta/okta-management-openapi-spec/blob/74fcd17fad54332caee96ebbb11fd7f203b03e4f/dist/current/management-dev-noEnums-minimal.yaml#L60548
github.com/okta/okta-developer-docs/blob/8aff3329cb8e651d2182ce6dcd5ebd303b42a690/packages/@okta/vuepress-site/books/api-security/api-keys/other-options/index.md#L18

Research log

redact-secret/redact-secret#694Research issue
redact-secret/redact-secret#315Research issue
redact-secret/redact-secret#1013Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/add1188fed9993723c59fbce8c867086b9d2049a/docs/audits/evidence/1013/okta-api-token.md