Fix Bug #3622: Fix OAuth authorisation code parsing and encoding during token redemption #3625
+9
−7
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
…g token redemption Fix an issue where OAuth authorisation codes containing non-alphanumeric characters were truncated or incorrectly transmitted during token redemption. The client now captures the full `code` query parameter from the redirect URI and ensures it is correctly form-encoded when posting to the token endpoint. Authorization codes are treated as opaque values and relayed exactly as returned by Microsoft, preventing AADSTS70000 errors caused by client-side parsing assumptions.
Owner
Author
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Repository owner
locked and limited conversation to collaborators
Feb 5, 2026
abraunegg
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Fix an issue where OAuth authorisation codes containing non-alphanumeric characters were truncated or incorrectly transmitted during token redemption.
The client now captures the full
codequery parameter from the redirect URI and ensures it is correctly form-encoded when posting to the token endpoint. Authorization codes are treated as opaque values and relayed exactly as returned by Microsoft, preventing AADSTS70000 errors caused by client-side parsing assumptions.