Daniel Weeks

@sammhho I don't think this is a problem with tomcat or with the scripts. The fact that you can see the application bar (blue) means that the data is there....

@othman-essabir it looks like timestamp is deprecated in ES 2.0+ See here: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-timestamp-field.html I'm not clear how much of an impact this would have, because it may rely on this...

Here's a complete example: ```java import java.net.URI; import org.junit.Test; import software.amazon.awssdk.auth.credentials.AwsBasicCredentials; import software.amazon.awssdk.auth.signer.Aws4Signer; import software.amazon.awssdk.auth.signer.internal.SignerConstant; import software.amazon.awssdk.auth.signer.params.Aws4SignerParams; import software.amazon.awssdk.auth.signer.params.SignerChecksumParams; import software.amazon.awssdk.core.checksums.Algorithm; import software.amazon.awssdk.http.SdkHttpFullRequest; import software.amazon.awssdk.http.SdkHttpMethod; import software.amazon.awssdk.regions.Region; public class TestSigV4Example...

According to the [SigV4 Documentation](https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html) > The x-amz-content-sha256 header is required for all AWS Signature Version 4 requests. It provides a hash of the request payload. If there is no...

> @danielcweeks Thank you for the repro code. When you say the signature verification fails, can you tell us where it fails, with which service? Can you give us more...

> The tests are failing because we have a few tests that use a parameterization that uses "avro" as the data file format. Currently we do this for all versions...

I think the application of extensions referenced in RFC 8693 are a little ambiguous due to the following: `RFC 6749` section 4.1 references the response described in [section 5.1](https://www.rfc-editor.org/rfc/rfc6749.html#section-5.1) `RFC...

@adutra > An RFC cannot modify another one's structs without officially superseding it. > . . . RFC 8693 as a general rewrite of RFC 6749 section 5.1 I'm not...

@wypoon Is this adding new artifacts as well? If the purpose is to have a single source set and validate across versions, we shouldn't be producing artifacts across all versions.

Hey @wypoon I think we're approaching this the wrong way. Rather than defining new projects to represent hive3&4, we can actually just run the tests against those dependencies by defining...