Fix OAuth2 PKCE Implementation Issues#19
Merged
Merged
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
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.
Problem
OAuth2 PKCE flows were broken due to:
Solution
https://x.com/i/oauth2/authorize, fix token endpoint to/2/oauth2/token, update defaultbase_urltohttps://api.x.com, and correct all documentation examplescode_challenge,code_challenge_method) in authorization URL when setChanges
python/oauth2_auth.j2: Fix authorization URL, token endpoint path, and default base_urlpython/main_client.j2: Update default base_urlpython/process_for_mintlify.j2: Fix documentation examples (imports, parameters, method usage)typescript/oauth2_auth.j2: Add PKCE parameters to authorization URLImpact
Testing