Skip to content

bridge: accept JSON whitespace in token responses - #11

Closed
Wondertan wants to merge 1 commit into
feat/ceremony-github-tokenfrom
fix/json-field-whitespace
Closed

Wondertan wants to merge 1 commit into
feat/ceremony-github-tokenfrom
fix/json-field-whitespace

Conversation

@Wondertan

Copy link
Copy Markdown
Member

Token-response layout construction and provider-error classification assumed compact JSON. Pin the whitespace-aware shared transcript reader from libid-rs #20, and classify the actual error field instead of searching raw response text. Reveal whitespace at its original offsets and commit only the bearer value.

Based on #8, which introduces the GitHub exchange; main does not contain that code. This PR is independent of callback-artifact retrieval (#9) and localhost/RC3 integration (#10), and preserves #8’s TLSN/MPZ pins.

Specification prerequisite: libid spec #32. Companion readers/verifiers: ceremony #28, contracts #36.

Validation: all 20 token-route tests pass on this independent branch using the pinned Rust revision; security/correctness, API and simplicity reviews are clear. This does not claim live OAuth or released-verifier qualification.

Pin the shared transcript reader and use its field extraction for provider error responses. Preserve existing TLSN/MPZ runtime dependencies.

Assisted-by: GPT-6
Signed-off-by: Wondertan <hlibwondertan@gmail.com>
SupremaLex added a commit that referenced this pull request Sep 11, 2026
Every comment, doc comment, README paragraph, example-file comment and
test doc in the crate now states the current behaviour or the meaning of a
value. History, rationale and review narration are removed.
`src/routes/github_token/transcript.rs` is left as is (#11 edits it).

Assisted-by: Claude Fable 5.1
Signed-off-by: SupremaLex <georglutsenko@gmail.com>
@Wondertan Wondertan closed this Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant