Missing required parameter [code_verifier]
See original GitHub issueawait authClient.requestAccessToken(code)
crashes with
error: {
error: 'invalid_request',
error_description: 'Missing required parameter [code_verifier].'
}
I think the problem is that #codeVerifier
is undefined
here 👇
https://github.com/twitterdev/twitter-api-typescript-sdk/blob/0d4954c675dbfc566c6911adc4d4178dce926ca4/src/OAuth2User.ts#L170
Issue Analytics
- State:
- Created a year ago
- Comments:14
Top Results From Across the Web
Issues · twitterdev/twitter-api-typescript-sdk - GitHub
Missing direct message support ... Missing tweets and no error raised by client when using searchStream ... Missing required parameter [code_verifier].
Read more >Missing parameter code_challenge_method - Stack Overflow
What you need to do is to: Generate a random value (code_verifier); Calculate the hash of that value (code_challenge); Send the code_challenge ...
Read more >Invalidate token oAuth2 v2 Code flow - Twitter Developers
I'm seeing a new error now: “”{"error":"invalid_request","error_description":"Missing required parameter [token_type_hint]."}“” Doc ...
Read more >OAuth2 and Twitter API - Questions - n8n community
As for OAuth2, this might require a closer look and will take some time ... error_description: 'Missing required parameter [code_verifier].
Read more >Ignore PKCE params for non-PKCE grants - GitLab.org
authRequest = { code_verifier, code_challenge }; const authUrl = client. ... invalid_request (The request is missing a required parameter, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sasivarnan The solution was fairly simple. In the initial call of generateAuthURL() I use code_challenge_method: ‘plain’ and save the code_challenge that I use. Then when the user is redirected back to my platform I call the generateAuthURL() method again with the same saved code_challenge, and then the requestAccessToken() method with the code I have received.
The
1.2.0
version published 6 days ago (thanks @refarer!) allows the token to be passed on the constructor. So, now you could do something like this:state
andchallenge
and callgenerateAuthURL
; persist these values to recreate the OAuth2User later on;state
andchallenge
and callrequestAccessToken
passing thecode
received; store the token returned by that function;Using firebase functions, my simplified code is: