fix(oauth): declare DCR application type - #1609
Merged
RhysSullivan merged 2 commits intoAug 28, 2026
Merged
Conversation
Merged
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
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.
Summary
webOAuth clientsnativeOAuth clientsContext
Some authorization servers validate redirect URIs against the registered
application_type. Executor already knows whether its callback is hosted or loopback, but did not include that metadata during dynamic client registration.The registration now sends the matching application type without changing client reuse or token handling.
Related to #770.
Verification
bun run format:checkbun run lintbun run typecheckcd packages/core/sdk && bun run test src/oauth-register-dynamic.test.tsThe changed SDK suite passes. The full repository run still reports three unrelated failures in
apps/cloud/src/account/org-api-key-revoke.node.test.ts.