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
Regression in v2.1262.0 - "Request is missing authentication token" #4286
Comments
See #4285 |
This is causing a lot of issues in the serverless world as well: |
solution- downgrade the SDK version untill the new release comes |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
The AWS SDK for JavaScript team is looking into this issue. If anyone has a minimal repro, please add it as an issue comment. |
The v2.1262.0 changelog for reference: https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md#212620 |
Commits between the releases v2.1261.0...v2.1262.0 The issue is likely in one of the following PRs: |
Commits between releases v2.1259.0...v2.1262.0 There were no custom changes released in |
Update: The team is currently working on pushing a fix. |
+1 |
Verified that fix from #4288 fixes the issue. Refer Pull request in https://github.com/trivikr/serverless-aws-bug/pull/1 |
+1 |
same here |
Release v2.1263.0 is out, and verified that "Request is missing Authentication Token" error is no longer thrown. |
Describe the bug
We are using serverless framework.
When trying deploy serverless framework application to aws, failed with "Request is missing authentication token".
SigV4 Authorization header not exists on v2.1262.0, it failed.
So i forcelly downgrade with aws-sdk version to v2.1261.0 and it worked as expected.
Expected Behavior
Properly generate and fill 'Authorization' header with AWS V4 Signature
Current Behavior
Invalid 'Authorization' header configured
Reproduction Steps
Make Cloudformation describeStacks API call
Possible Solution
No response
Additional Information/Context
No response
SDK version used
v2.1262.0
Environment details (OS name and version, etc.)
debian 9, node 12.22.5
The text was updated successfully, but these errors were encountered: