Fix Auth Consent scopes issue #4733
Merged
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.
Impact: major
Type: bugfix
Issues
openidscope is added at the beginning of the auth flow by the consumer app, and there is no issuance of an id_token on completion of the auth. This was also preventing refresh-tokens from being granted (seen while fixing Enable access token refreshing example-storefront#350)Solution
getConsentcall to retrieve the list of the client-requested scope, and pass them when granting the consent in theacceptConsentRequestcall.Testing