feat: Make the token exchange in pre-authorized-code-flow with a form… #2
Conversation
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
…-encoded request The spec https://www.rfc-editor.org/rfc/rfc6749.html#section-4.1.3 explicitly mentions it must be a form-encoded request. One of our issuers - veramo-core - only handles form-encoded token requests in the pre-authorized-code-flow when done with such a form-encoded body and header.
berkes
force-pushed
the
wip/verify-token-exchange-form-encoded
branch
from
a39c312 to
fb9a5c2
Compare
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.
…-encoded request
The spec https://www.rfc-editor.org/rfc/rfc6749.html#section-4.1.3 explicitly mentions it must be a form-encoded request. One of our issuers - veramo-core - only handles form-encoded token requests in the pre-authorized-code-flow when done with such a form-encoded body and header.