feat(oauth): log redirect target on authorization code issuance - #24
Merged
Merged
Conversation
ChatGPT's connector stalled after receiving an authorization code and never exchanged it; the log showed pairing success and silence, with no visibility into where the browser was actually redirected. Issuance now logs the redirect target so hand-off failures are diagnosable.
willio
added a commit
that referenced
this pull request
Sep 1, 2026
feat(oauth): log redirect target on authorization code issuance
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the redirect target to the pairing-verified log line, closing a diagnostic blind spot found while debugging a ChatGPT connector that received an authorization code but never exchanged it.