FI-3026: Fix Granular Scopes Group Token Exchange Requested Scopes Warning #568
Conversation
This file contains 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.
Summary
To pass the SMART Granular Scope Selection group, it is necessary not to grant all requested scopes, but the test titled: 'Token exchange response body contains required information encoded in JSON' was warning users that not all requested scopes were granted.
This PR updates the SMART Granular Scope Selection group so that it adds the
ignore_missing_scopes_checkoption to the importedsmart_standalone_launch_stu2test group so that the warning is not displayed.Testing Guidance
Run the SMART Granular Scope Selection group, and ensure that not granting all the requested scopes no longer adds a warning to the test titled: 'Token exchange response body contains required information encoded in JSON'.