Support URL-based downstream OAuth clients - #621
Merged
Merged
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
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.
Basecamp advertises URL-based OAuth client IDs but rejects Connecta's HTTPS callback during dynamic client registration. Expose the SDK's
clientMetadataUrland default scope settings so deployments can authorize through a public client metadata document and retain the existing PKCE, issuer binding, encrypted token storage, refresh, and disconnect behavior.Invalid metadata URLs and scope strings fail at construction. The settings participate in the retained-client configuration binding. Bumps the package and Node template to 0.26.3.
Validation:
npm run release:checkpassed: 4,811 tests, 50 browser tests, package and Docker smoke checks, and zero production dependency vulnerabilities. OAuth tests cover URL-client code exchange, scopes, and the existing registration path. Basecamp's live pushed-authorization endpoint accepted One&Many's hosted metadata, exact callback, andfull mcp offline_accessscopes.