fix(oauth2): allow users to approve scope changes - #38942
Open
Harsh-128 wants to merge 4 commits into
Open
Conversation
Member
|
It's better to have a hint about the scopes changed in the confirm dialog. |
Author
|
Thanks for the suggestion. I’ll update the confirm dialog to provide a clear hint when the OAuth2 scopes have changed. |
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
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.
This fixes the OAuth2 flow when an existing grant has a different scope from the requested scope.
Previously, users with an existing grant could get an error when an application requested a different scope. Confidential or trusted applications could also reuse the existing grant without showing the consent page.
This change:
Tests:
Fixes #38940.