Promote foss-sandbox to foss-main: fix MCP OAuth redirect after sign-in - #23
Merged
Conversation
When an unauthenticated user hits /authorize during MCP OAuth, PageChangeEffect discards the full URL (client_id, redirect_uri, state, code_challenge) and redirects to /sign-in-up. After login the user lands on the homepage instead of returning to the OAuth consent page. Encode the full /authorize?... URL as returnToPath so the existing post-login redirect mechanism routes back to the consent flow.
Preserve OAuth authorize URL through sign-in redirect
LogDetails |
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.
Description
Promotes foss-sandbox changes to foss-main, including the MCP OAuth redirect fix: when an unauthenticated user hits
/authorizeduring MCP OAuth (e.g. from Claude.ai), the full OAuth URL is now preserved asreturnToPaththrough the sign-in flow. Previously the user landed on the homepage after login instead of returning to the OAuth consent page.