-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Improve discoverability of the timeout parameter for fetch requests (in docs and/or code) #133
Comments
Seems like the problem is a timeout after 1500 which is the default.
|
Seems like the problem is a timeout after 1500 which is the default.
Is it possible to expose timeout setting to the user? |
The timeout is user exposed: https://github.com/awslabs/aws-jwt-verify#configuring-the-jwks-response-timeout-and-other-http-options-with-jsonfetcher See also this comment: #72 (comment) Let's leave this issue open because you have convinced me we need to do a better job of making this setting more obvious. |
Describe the bug
Please provide a clear and concise description of what the bug is.
Trying to decode a token generated by Cognito results in Failed to fetch jwks.
I've double checked all credentials (AWS_COGNITO_USER_POOL_ID, AWS_COGNITO_CLIENT_ID)
fetch the raw URL of the jwks from amazon works well - The json is retrieved.
Versions
Which version of
aws-jwt-verify
are you using? 4.0.0Are you using the library in Node.js or in the Web browser? Postman/Browser
If Node.js, which version of Node.js are you using? (Should be at least 14)
If Web browser, which web browser and which version of it are you using? 20.4.0
If using TypeScript, which version of TypeScript are you using? (Should be at least 4) 5.1.6
To Reproduce
If you can, please provide a minimal code example that reproduces the bug.
const decoded = await verifier.verify(token);
The text was updated successfully, but these errors were encountered: