Details
Assignee
Michael OffnerMichael OffnerReporter
Matthew ClementeMatthew ClementePriority
NewLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Matthew Clemente
Matthew ClementePriority
Labels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created last month
Updated 2 days ago
This is covered in a Dev forum post here: Issue with AWS Java SDK v2 and Lucee 6
From that post:
We’re using the AWS Java SDK v2 and are seeing a difference in behavior between Lucee 5 and Lucee 6.
It was working on the lambdacfc project where I noticed this issue.
Here’s a stripped down repro case: GitHub - mjclemente/test_lucee_6_aws_sdk_jar_issue: Trying to debug an issue with Lucee 6 and the AWS Java SDK v2 1
If you run the repro with Lucee 5.4.7+2, it returns the class
software.amazon.awssdk.auth.credentials.AwsBasicCredentials
, which is expected.If you run it with Lucee 6.2.1.77, it returns
software.amazon.awssdk.identity.spi.internal.DefaultAwsCredentialsIdentity
, and it seems it’s not possible to use the static methods to return anAwsCredentialsIdentity
. Consequently, it throws a wrench in authenticating with AWS.You can see the issue with Lucee 6 on TryCF as well: https://trycf.com/gist/79e14139f5b67a419fe55d42ac3a38ad/lucee6?theme=monokai