#56 Fixes backchannel and JwtTokens with System.Text.Json#57
Open
enkelmedia wants to merge 1 commit into
Open
Conversation
Author
|
If someone wants to run a patched version until this has been included in a release, here is how.
|
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 PR fixes the issue with JSON formatting in the BackChannel logout payload described here: #56
IdentityServer has historically recommended that implement BachChannel logout parses the
eventsproperty like this:This would require a valid JSON payload for the logout token, like so
However, at some point when Microsoft switched from using
Newtonsoft.JsontoSystem.Text.Jsonthe seriliazation started to fail, producing JSON payloads like this:This payload is invalid, and the value(s) for the event property get discarded.
This PR fixes this by:
Updating
TokenExtensions.CreateJwtPayloadto use types fromSystem.Text.Json. This way theJwtSecurityTokenHandlerinDefaultTokenCreationServicecan serialize to a valid JSON payload.I've also:
ClientCredentialsClient.csthat was validating a invalid payload (false positive). Details:cnfproperty should be a object not an array according to the spec.