Fix json deserialization of multi-valued authorization request parameters #1676
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
spring-projects-issues
added
the
status: waiting-for-triage
MrJovanovic13
force-pushed
the
gh-1666
branch
2 times, most recently
from
f6830f9
to
c18e8b3
Compare
jgrandja
changed the title
jgrandja
added
type: bug
|
Thanks for the fix @MrJovanovic13 ! This is now merged. |
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.
I have tested this mixin on a sample spring authorization server app, by registering the mixin on a custom JdbcOAuth2AuthorizationService bean.
Authorization flow now works correctly without throwing on multi valued parameters. String[] is correctly serialized & deserialized.
Closes gh-1666