You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when setting the challenge method to s256, it does not respect the code_challenge provided. For this reason, I won't be able to send a code_verifier later to the oauth authorizer for a proper token exchange.
exporttypeGenerateAuthUrlOptions={/** A random string you provide to verify against CSRF attacks. The length of this string can be up to 500 characters. */state: string;/** A PKCE parameter, a random secret for each request you make. */
code_challenge: string;/** Specifies the method you are using to make a request (S256 OR plain). */
code_challenge_method: "plain"|"s256";};
The text was updated successfully, but these errors were encountered:
tansanDOTeth
changed the title
Code Challenge is missing when Code Challenge Method is plain
Code Challenge is missing when Code Challenge Method is s256
Mar 21, 2024
Currently, when setting the challenge method to
s256
, it does not respect thecode_challenge
provided. For this reason, I won't be able to send acode_verifier
later to the oauth authorizer for a proper token exchange.Specific to the code here: https://github.com/twitterdev/twitter-api-typescript-sdk/blob/0d12a20a76d6dd9c346decf9cc80bc611975d43f/src/OAuth2User.ts#L45C2-L58C7
It should be:
Related Spec:
https://www.rfc-editor.org/rfc/rfc7636#section-4.6
The text was updated successfully, but these errors were encountered: