fix: correct redirect URI in client-metadata.json #585
+1
−1
Conversation
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
Update redirect_uris entry to the intended callback URL
Contributor
Author
|
@alexhancock I’ve updated the redirect_uris in metadata.json to correct the previously incorrect port configuration that was breaking the flow and causing the error: “invalid_request: redirect_uri MUST exactly match one of the registered redirect_uris.” Please include this change as well and merge it. |
Contributor
Author
|
@jokemanfire can you also look into it |
alexhancock
approved these changes
Dec 15, 2025
Contributor
Author
|
@alexhancock Thanks Everything works now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Switch client-metadata.json to the 127.0.0.1:8080 callback URL for local OAuth flows
Breaking Changes
No
Types of changes
Checklist
Additional context
Fix #570