-
Notifications
You must be signed in to change notification settings - Fork 35
fix(oauth): filter unsupported scopes before parsing #203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
andrewsouthard
wants to merge
3
commits into
ascorbic:main
Choose a base branch
from
andrewsouthard:fix/scope-parse-filter-unrecognized
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The filtering happens here, but nothing consumes it. Every caller ignores the return value and keeps the raw string:
par.ts~L186:params.scope = scope(raw), thenparseScope(scope)result droppedprovider.ts~L382 (authorize GET): sameprovider.ts~L524:scope = requestedScopegoes intoauthCodeData.scopeprovider.ts~L1122 (authorize POST): samegenerateTokens({ scope: codeData.scope })and it rides through refreshReproduced on this branch with a full PAR → consent → token flow using
atproto repo:com.example.thing?action=read madeup:thing include:bad: PAR 201, consent 200, and the token response is"scope": "atproto repo:com.example.thing?action=read madeup:thing include:bad"— junk and all.That matters for three reasons: the token response's
scopedoesn't reflect what was granted (RFC 6749 §5.1);include:badsneaks past theallowIncludescheck below because it's filtered out before that loop runs; and — the one I actually care about — a scope we can't parse today gets stored verbatim and becomes a live permission the day@atproto/oauth-scopesis bumped to a version that understands it, without ever appearing on the consent screen. The reference implementation doesparameters = { ...parameters, scope }to replace the stored value with the filtered one for exactly this reason.Suggest: return (or expose) the filtered scope string and assign it back to
params.scope/scopeat those four sites before anything is stored.