Repository navigation
Conversation
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://kjohnson-oauth-loopback-callback-ports.previews.developers.cloudflare.com (commit 47c6d03)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Contributor
Typically, changelog entries should be dated the day they merge. This is not blocking — if the date is unintentional, please update it. |
Michael9127
reviewed
Oct 15, 2026
| http://127.0.0.1:49152/callback | ||
| ``` | ||
|
|
||
| Only the port can change. The scheme, host, path, and query must match exactly. The exception applies to `127.0.0.1`, `[::1]`, and explicitly registered `localhost` callbacks. Public clients must use PKCE with `S256`. If the port changes, the token exchange must include the exact `redirect_uri` used during authorization. |
Contributor
There was a problem hiding this comment.
If we do want a changelog for this, we should probably call out that the port does need to remain the same between authorization and token exchange.
Contributor
There was a problem hiding this comment.
Public clients must use PKCE with
S256
I would call out more clearly that this constraint only applies to the loosening of port checks
Michael9127
reviewed
Oct 15, 2026
| - `[::1]` | ||
| - `localhost`, when explicitly registered | ||
|
|
||
| Only the port can change. The scheme (`http` or `https`), host, path, and query must match the registered URI exactly. For example, a client registered with `http://127.0.0.1:3000/callback` can authorize with `http://127.0.0.1:49152/callback`, but not `http://localhost:49152/callback` or a different callback path. Non-loopback redirect URIs still require an exact registered match. |
Contributor
There was a problem hiding this comment.
same as above, port can only change during registration. it needs to be consistent between token exchange an authorization
Michael9127
suggested changes
Oct 15, 2026
Contributor
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
3 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.
Summary
Documents dynamic loopback callback ports for Managed OAuth and MCP portal clients, including IPv6 loopback, port-only matching, and the authorization-time callback required at token exchange.
Keeps client callbacks separate from upstream server callbacks and adds a changelog entry.
Documentation checklist