search

eclipse-store / store

High-Performance Java-Native-Persistence. Store and load any Java Object Graph or Subgraphs partially, Relieved of Heavy-weight JPA. Microsecond Response Time. Ultra-High Throughput. Minimum of Latencies. Create Ultra-Fast In-Memory Database Applications & Microservices.
https://eclipsestore.io/
Eclipse Public License 2.0
183 stars 17 forks source link

Minio and EclipseStore fail with Message: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. (Service: S3, Status Code: 400 #223

Closed sdelamo closed 3 weeks ago

sdelamo commented 3 months ago

Steps to reproduce.

Clone branch eclipsestore_1_3_2 in the repository https://github.com/micronaut-projects/micronaut-eclipsestore

Run ./gradlew :micronaut-eclipsestore:test --tests "io.micronaut.eclipsestore.s3.S3StorageSpec"

The test fails with: 


io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.micronaut.eclipsestore.BaseStorageSpec$CustomerRepository]

Message: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. (Service: S3, Status Code: 400, Request ID: 17D590734D1B49AA, Extended Request ID: dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8)
Path Taken: S3StorageSpec.setCustomerRepository([CustomerRepository customerRepository]) --> new CustomerRepository([StorageManager storageManager])
    at app//io.micronaut.context.DefaultBeanContext.resolveByBeanFactory(DefaultBeanContext.java:2331)
    at app//io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2286)
    at app//io.micronaut.context.DefaultBeanContext.doCreateBean(DefaultBeanContext.java:2298)

I assume this is caused by :

https://github.com/eclipse-store/store/pull/197

SimonFrauenschuh commented 3 months ago

In the micronaut implementation, they were able to use mino like that.

If you remove the s3.test property (--> standard client is used), it fails with the exact same error message

zdenek-jonas commented 2 months ago

Could you test it again with version 1.4.0?

SimonFrauenschuh commented 1 month ago

In the 1.7.x branch, where Eclipsestore v1.4.0 is used, no error is thrown in this test