Skip to content
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

Upgrade to 1.0.38 fails #1184

Closed
steamstreetjon opened this issue Jan 21, 2024 · 3 comments
Closed

Upgrade to 1.0.38 fails #1184

steamstreetjon opened this issue Jan 21, 2024 · 3 comments
Labels
bug This issue is a bug.

Comments

@steamstreetjon
Copy link

Describe the bug

When upgrading to 1.0.38, the following exception occurs:

aws.smithy.kotlin.runtime.auth.awssigning.UnsupportedSigningAlgorithmException: SIGV4_ASYMMETRIC support is not yet implemented for the default signer.

1.0.37 works fine.

Expected behavior

The exception should not be thrown.

Current behavior

Calls with the EventBridge client are failing. Others may be as well.

Steps to Reproduce

Update AWS KT dependency to 1.0.38 or greater. Make an API call.

Possible Solution

No response

Context

No response

AWS Kotlin SDK version used

1.0.38

Platform (JVM/JS/Native)

JVM

Operating System and version

Lambda Java 17

@steamstreetjon steamstreetjon added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jan 21, 2024
@lauzadis
Copy link
Member

Thanks for the report, I replicated the failure and working on a fix.

@lauzadis lauzadis removed the needs-triage This issue or PR still needs to be triaged. label Jan 22, 2024
@lauzadis
Copy link
Member

Hi, this is fixed in the latest version of the SDK, v1.0.42. Thanks again for the report.

Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants