Skip to content

M1 acceptance gate: persisted client_credentials client gets a token (#25) - #113

Merged
stephane-segning merged 1 commit into
mainfrom
claude/25-m1-acceptance-gate
Aug 3, 2026
Merged

M1 acceptance gate: persisted client_credentials client gets a token (#25)#113
stephane-segning merged 1 commit into
mainfrom
claude/25-m1-acceptance-gate

Add #25's M1 acceptance gate: a persisted client_credentials client s…

58c041d
Select commit
Loading
Failed to load commit list.
Lightbridge Assistant / Lightbridge Review succeeded Aug 3, 2026 in 2m 0s

No findings

No findings on this diff.

Reviewed both changed source files in full. app/sms-gateway/Cargo.toml adds only a [dev-dependencies] block whose eight entries all resolve to existing, correctly-versioned [workspace.dependencies] entries (base64, chrono, jsonwebtoken, rand, reqwest, rsa, serde, serde_json), inheriting the right features (jsonwebtoken's rust_crypto backend, reqwest's json+rustls-tls) with no dependency-tree forking, secrets, or CVE-relevant bumps. The new m1_acceptance_gate_live_postgres.rs is an #[ignore]d live-Postgres acceptance test whose RSA keys and hand-signed developer token are runtime-generated test-only stand-ins (not committed secrets); I verified the msisdn formatting, the SIGKILL/OS-process-restart seam, the missing-kid single-key JWKS path, scope echo, and the FORBIDDEN-with-permission-name denial — all correct. SAST reports no findings. No defects found; clean pass.